linux-kernel - Re: [PATCH] ASoC: SMA1303: set sma_i2c_regmap storage-class-specifier to static

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: <167873446131.106067.2236196636490693766.b4-ty@kernel.org>
Date:   Mon, 13 Mar 2023 19:07:41 +0000
From:   Mark Brown <broonie@...nel.org>
To:     kiseok.jo@...ndevice.com, lgirdwood@...il.com, perex@...ex.cz,
        tiwai@...e.com, Tom Rix <trix@...hat.com>
Cc:     alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: SMA1303: set sma_i2c_regmap
 storage-class-specifier to static

On Thu, 09 Mar 2023 09:09:59 -0500, Tom Rix wrote:
> smatch reports
> sound/soc/codecs/sma1303.c:1594:28:
>   warning: symbol 'sma_i2c_regmap' was not declared. Should it be static?
> 
> sma_i2c_regmap is only used in sma1303, so it should be static
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: SMA1303: set sma_i2c_regmap storage-class-specifier to static
      commit: d7d103d1779c3d0bc4d55f2802930a6b067450c0

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