linux-kernel - Re: [PATCH] regmap: fix the kerneldoc for regmap_test

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: <159162037977.23406.68181793825135924.b4-ty@kernel.org>
Date:   Mon, 08 Jun 2020 13:46:19 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Bartosz Golaszewski <brgl@...ev.pl>
Cc:     Bartosz Golaszewski <bgolaszewski@...libre.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regmap: fix the kerneldoc for regmap_test_bits()

On Sun, 7 Jun 2020 11:34:21 +0200, Bartosz Golaszewski wrote:
> The kerneldoc comment for regmap_test_bits() says that it returns -1 on
> regmap_read() failure. This is not true - it will propagate the error
> code returned by regmap_read(). Fix it.

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next

Thanks!

[1/1] regmap: fix the kerneldoc for regmap_test_bits()
      commit: e680a4098f6404191e0e438a9758715b0bff6d7f

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