linux-kernel - Re: [PATCH v1 1/1] ASoC: soc-ac97: Return correct error codes

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: <167650979440.3620645.14876076040377125402.b4-ty@kernel.org>
Date:   Thu, 16 Feb 2023 01:09:54 +0000
From:   Mark Brown <broonie@...nel.org>
To:     alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc:     Liam Girdwood <lgirdwood@...il.com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>,
        kernel test robot <lkp@...el.com>,
        Dan Carpenter <error27@...il.com>
Subject: Re: [PATCH v1 1/1] ASoC: soc-ac97: Return correct error codes

On Wed, 15 Feb 2023 15:23:43 +0200, Andy Shevchenko wrote:
> With the switching to dev_err_probe(), during the conversion
> of GPIO calls, the return code is passed is a paratemer to it.
> At the same time a copy'n'paste mistake was made, so the wrong
> variable has been taken for the error reporting. Fix this.
> 
> 

Applied to

   broonie/sound.git for-next

Thanks!

[1/1] ASoC: soc-ac97: Return correct error codes
      commit: 76f5aaabce492aa6991c28c96bb78b00b05d06c5

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