From: Guochun Mao <guochun.mao@mediatek.com>
To: Mark Brown <broonie@kernel.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: <srv_heupstream@mediatek.com>, <linux-kernel@vger.kernel.org>,
<linux-spi@vger.kernel.org>, <linux-mediatek@lists.infradead.org>,
Bin Zhang <bin.zhang@mediatek.com>,
<project_global_chrome_upstream_group@mediatek.com>,
kernel test robot <lkp@intel.com>,
Bayi Cheng <bayi.cheng@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Chuanhong Guo <gch981213@gmail.com>
Subject: Re: [PATCH] spi: spi-mtk-nor: make some internal variables static
Date: Fri, 28 Jan 2022 09:02:44 +0800 [thread overview]
Message-ID: <c847fc0055557ac362305b2689caf14cd96a4fe0.camel@mediatek.com> (raw)
In-Reply-To: <164321141754.490431.3020669404541003433.b4-ty@kernel.org>
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@mediatek.com wrote:
> > From: Guochun Mao <guochun.mao@mediatek.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
next prev parent reply other threads:[~2022-01-28 1:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 9:11 guochun.mao
2022-01-26 15:36 ` Mark Brown
2022-01-28 1:02 ` Guochun Mao [this message]
2022-01-27 11:52 ` AngeloGioacchino Del Regno
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c847fc0055557ac362305b2689caf14cd96a4fe0.camel@mediatek.com \
--to=guochun.mao@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bayi.cheng@mediatek.com \
--cc=bin.zhang@mediatek.com \
--cc=broonie@kernel.org \
--cc=gch981213@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=lkp@intel.com \
--cc=matthias.bgg@gmail.com \
--cc=project_global_chrome_upstream_group@mediatek.com \
--cc=srv_heupstream@mediatek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®