linux-kernel - Re: [PATCH] regmap: mmio: replace return 0 with break in switch statement

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: <166386924264.727940.17683368538547591702.b4-ty@kernel.org>
Date:   Thu, 22 Sep 2022 18:54:02 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Colin Ian King <colin.i.king@...il.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "Rafael J . Wysocki" <rafael@...nel.org>
Cc:     linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH] regmap: mmio: replace return 0 with break in switch statement

On Thu, 22 Sep 2022 09:04:45 +0100, Colin Ian King wrote:
> Variable min_stride is assigned a value that is never read, fix this by
> replacing the return 0 with a break statement. This also makes the case
> statement consistent with the other cases in the switch statement.
> 
> 

Applied to

   broonie/regmap.git for-next

Thanks!

[1/1] regmap: mmio: replace return 0 with break in switch statement
      commit: 01ed230761e51f0403b3f3845c11cb67014487e2

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