From: Miquel Raynal <miquel.raynal@bootlin•com>
To: YueHaibing <yuehaibing@huawei•com>
Cc: christophe.kerello@st•com, alexandre.torgue@st•com,
bbrezillon@kernel•org, richard@nod•at,
linux-kernel@vger•kernel.org, marek.vasut@gmail•com,
linux-mtd@lists•infradead.org, mcoquelin.stm32@gmail•com,
computersforpeace@gmail•com, dwmw2@infradead•org,
linux-stm32@st-md-mailman•stormreply.com,
linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH -next] mtd: rawnand: stm32_fmc2: Make some functions static
Date: Tue, 5 Feb 2019 20:06:17 +0100 [thread overview]
Message-ID: <20190205200617.087f3e4a@xps13> (raw)
In-Reply-To: <20190130100908.19532-1-yuehaibing@huawei.com>
Hi Yue,
YueHaibing <yuehaibing@huawei•com> wrote on Wed, 30 Jan 2019 18:09:08
+0800:
> Fixes the following sparse warning:
> drivers/mtd/nand/raw/stm32_fmc2_nand.c:1228:6: warning: symbol 'stm32_fmc2_read_data' was not declared. Should it be static?
> drivers/mtd/nand/raw/stm32_fmc2_nand.c:1275:6: warning: symbol 'stm32_fmc2_write_data' was not declared. Should it be static?
> drivers/mtd/nand/raw/stm32_fmc2_nand.c:1707:32: warning: symbol 'stm32_fmc2_nand_ooblayout_ops' was not declared. Should it be static?
>
> Signed-off-by: YueHaibing <yuehaibing@huawei•com>
> ---
Merged in nand/next with the original commit.
Thanks,
Miquèl
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-02-05 19:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 10:09 [PATCH -next] mtd: rawnand: stm32_fmc2: Make some functions static YueHaibing
2019-01-30 10:34 ` Miquel Raynal
2019-01-30 10:43 ` YueHaibing
2019-02-05 19:06 ` Miquel Raynal [this message]
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=20190205200617.087f3e4a@xps13 \
--to=miquel.raynal@bootlin$(echo .)com \
--cc=alexandre.torgue@st$(echo .)com \
--cc=bbrezillon@kernel$(echo .)org \
--cc=christophe.kerello@st$(echo .)com \
--cc=computersforpeace@gmail$(echo .)com \
--cc=dwmw2@infradead$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mtd@lists$(echo .)infradead.org \
--cc=linux-stm32@st-md-mailman$(echo .)stormreply.com \
--cc=marek.vasut@gmail$(echo .)com \
--cc=mcoquelin.stm32@gmail$(echo .)com \
--cc=richard@nod$(echo .)at \
--cc=yuehaibing@huawei$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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