linux-kernel - Re: [PATCH] spi: spi-mtk-nor: make some internal variables 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: <c847fc0055557ac362305b2689caf14cd96a4fe0.camel@mediatek.com>
Date:   Fri, 28 Jan 2022 09:02:44 +0800
From:   Guochun Mao <guochun.mao@...iatek.com>
To:     Mark Brown <broonie@...nel.org>,
        AngeloGioacchino Del Regno 
        <angelogioacchino.delregno@...labora.com>
CC:     <srv_heupstream@...iatek.com>, <linux-kernel@...r.kernel.org>,
        <linux-spi@...r.kernel.org>, <linux-mediatek@...ts.infradead.org>,
        Bin Zhang <bin.zhang@...iatek.com>,
        <project_global_chrome_upstream_group@...iatek.com>,
        kernel test robot <lkp@...el.com>,
        Bayi Cheng <bayi.cheng@...iatek.com>,
        Matthias Brugger <matthias.bgg@...il.com>,
        Chuanhong Guo <gch981213@...il.com>
Subject: Re: [PATCH] spi: spi-mtk-nor: make some internal variables static

Hi,

Thank you very much.

BR,
Guochun


On Wed, 2022-01-26 at 15:36 +0000, Mark Brown wrote:
> On Wed, 26 Jan 2022 17:11:59 +0800, guochun.mao@...iatek.com wrote:
> > From: Guochun Mao <guochun.mao@...iatek.com>
> > 
> > Variables mtk_nor_caps_mt8173, mtk_nor_caps_mt8186 and
> > mtk_nor_caps_mt8192 are not declared.
> > Make them static.
> > 
> > 
> > [...]
> 
> Applied to
> 
>    https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
> for-next
> 
> Thanks!
> 
> [1/1] spi: spi-mtk-nor: make some internal variables static
>       commit: 474fc2e6395d62758e80b9ea65f61339296355fc
> 
> 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