linux-kernel - Re: [PATCH v1 1/1] spi: mpc5xxx-psc: Remove goto to the unexisted label

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <167846056875.924688.11655271939766506433.b4-ty@kernel.org>
Date:   Fri, 10 Mar 2023 15:02:48 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc:     kernel test robot <lkp@...el.com>
Subject: Re: [PATCH v1 1/1] spi: mpc5xxx-psc: Remove goto to the unexisted
 label

On Fri, 10 Mar 2023 13:15:44 +0200, Andy Shevchenko wrote:
> The previous cleanup patch had lost one of its parts in a crack,
> Finish the cleanup by removing the leftovers.
> 
> 

Applied to

   broonie/spi.git for-next

Thanks!

[1/1] spi: mpc5xxx-psc: Remove goto to the unexisted label
      commit: 21d19e601fd221cd61105286b0b6ec2f9c5a2576

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark