All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 30 Jan 2019 11:34:28 +0100	[thread overview]
Message-ID: <20190130113428.37570a55@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>
> ---
>  drivers/mtd/nand/raw/stm32_fmc2_nand.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/mtd/nand/raw/stm32_fmc2_nand.c b/drivers/mtd/nand/raw/stm32_fmc2_nand.c
> index e057282..999ca6a 100644
> --- a/drivers/mtd/nand/raw/stm32_fmc2_nand.c
> +++ b/drivers/mtd/nand/raw/stm32_fmc2_nand.c
> @@ -1225,8 +1225,8 @@ static irqreturn_t stm32_fmc2_irq(int irq, void *dev_id)
>  	return IRQ_HANDLED;
>  }
>  
> -void stm32_fmc2_read_data(struct nand_chip *chip, void *buf,
> -			  unsigned int len, bool force_8bit)
> +static void stm32_fmc2_read_data(struct nand_chip *chip, void *buf,
> +				 unsigned int len, bool force_8bit)
>  {
>  	struct stm32_fmc2_nfc *fmc2 = to_stm32_nfc(chip->controller);
>  	void __iomem *io_addr_r = fmc2->data_base[fmc2->cs_sel];
> @@ -1272,8 +1272,8 @@ void stm32_fmc2_read_data(struct nand_chip *chip, void *buf,
>  		stm32_fmc2_set_buswidth_16(fmc2, true);
>  }
>  
> -void stm32_fmc2_write_data(struct nand_chip *chip, const void *buf,
> -			   unsigned int len, bool force_8bit)
> +static void stm32_fmc2_write_data(struct nand_chip *chip, const void *buf,
> +				  unsigned int len, bool force_8bit)
>  {
>  	struct stm32_fmc2_nfc *fmc2 = to_stm32_nfc(chip->controller);
>  	void __iomem *io_addr_w = fmc2->data_base[fmc2->cs_sel];
> @@ -1704,7 +1704,7 @@ static int stm32_fmc2_nand_ooblayout_free(struct mtd_info *mtd, int section,
>  	return 0;
>  }
>  
> -const struct mtd_ooblayout_ops stm32_fmc2_nand_ooblayout_ops = {
> +static const struct mtd_ooblayout_ops stm32_fmc2_nand_ooblayout_ops = {
>  	.ecc = stm32_fmc2_nand_ooblayout_ecc,
>  	.free = stm32_fmc2_nand_ooblayout_free,
>  };

This is nand/next material, so if you don't mind I would like to squash
this fix into the original commit inserting the driver.


Thanks,
Miquèl

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

WARNING: multiple messages have this Message-ID (diff)
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: Wed, 30 Jan 2019 11:34:28 +0100	[thread overview]
Message-ID: <20190130113428.37570a55@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>
> ---
>  drivers/mtd/nand/raw/stm32_fmc2_nand.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/mtd/nand/raw/stm32_fmc2_nand.c b/drivers/mtd/nand/raw/stm32_fmc2_nand.c
> index e057282..999ca6a 100644
> --- a/drivers/mtd/nand/raw/stm32_fmc2_nand.c
> +++ b/drivers/mtd/nand/raw/stm32_fmc2_nand.c
> @@ -1225,8 +1225,8 @@ static irqreturn_t stm32_fmc2_irq(int irq, void *dev_id)
>  	return IRQ_HANDLED;
>  }
>  
> -void stm32_fmc2_read_data(struct nand_chip *chip, void *buf,
> -			  unsigned int len, bool force_8bit)
> +static void stm32_fmc2_read_data(struct nand_chip *chip, void *buf,
> +				 unsigned int len, bool force_8bit)
>  {
>  	struct stm32_fmc2_nfc *fmc2 = to_stm32_nfc(chip->controller);
>  	void __iomem *io_addr_r = fmc2->data_base[fmc2->cs_sel];
> @@ -1272,8 +1272,8 @@ void stm32_fmc2_read_data(struct nand_chip *chip, void *buf,
>  		stm32_fmc2_set_buswidth_16(fmc2, true);
>  }
>  
> -void stm32_fmc2_write_data(struct nand_chip *chip, const void *buf,
> -			   unsigned int len, bool force_8bit)
> +static void stm32_fmc2_write_data(struct nand_chip *chip, const void *buf,
> +				  unsigned int len, bool force_8bit)
>  {
>  	struct stm32_fmc2_nfc *fmc2 = to_stm32_nfc(chip->controller);
>  	void __iomem *io_addr_w = fmc2->data_base[fmc2->cs_sel];
> @@ -1704,7 +1704,7 @@ static int stm32_fmc2_nand_ooblayout_free(struct mtd_info *mtd, int section,
>  	return 0;
>  }
>  
> -const struct mtd_ooblayout_ops stm32_fmc2_nand_ooblayout_ops = {
> +static const struct mtd_ooblayout_ops stm32_fmc2_nand_ooblayout_ops = {
>  	.ecc = stm32_fmc2_nand_ooblayout_ecc,
>  	.free = stm32_fmc2_nand_ooblayout_free,
>  };

This is nand/next material, so if you don't mind I would like to squash
this fix into the original commit inserting the driver.


Thanks,
Miquèl

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: YueHaibing <yuehaibing@huawei.com>
Cc: <bbrezillon@kernel.org>, <richard@nod.at>, <dwmw2@infradead.org>,
	<computersforpeace@gmail.com>, <marek.vasut@gmail.com>,
	<mcoquelin.stm32@gmail.com>, <alexandre.torgue@st.com>,
	<christophe.kerello@st.com>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	<linux-mtd@lists.infradead.org>
Subject: Re: [PATCH -next] mtd: rawnand: stm32_fmc2: Make some functions static
Date: Wed, 30 Jan 2019 11:34:28 +0100	[thread overview]
Message-ID: <20190130113428.37570a55@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>
> ---
>  drivers/mtd/nand/raw/stm32_fmc2_nand.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/mtd/nand/raw/stm32_fmc2_nand.c b/drivers/mtd/nand/raw/stm32_fmc2_nand.c
> index e057282..999ca6a 100644
> --- a/drivers/mtd/nand/raw/stm32_fmc2_nand.c
> +++ b/drivers/mtd/nand/raw/stm32_fmc2_nand.c
> @@ -1225,8 +1225,8 @@ static irqreturn_t stm32_fmc2_irq(int irq, void *dev_id)
>  	return IRQ_HANDLED;
>  }
>  
> -void stm32_fmc2_read_data(struct nand_chip *chip, void *buf,
> -			  unsigned int len, bool force_8bit)
> +static void stm32_fmc2_read_data(struct nand_chip *chip, void *buf,
> +				 unsigned int len, bool force_8bit)
>  {
>  	struct stm32_fmc2_nfc *fmc2 = to_stm32_nfc(chip->controller);
>  	void __iomem *io_addr_r = fmc2->data_base[fmc2->cs_sel];
> @@ -1272,8 +1272,8 @@ void stm32_fmc2_read_data(struct nand_chip *chip, void *buf,
>  		stm32_fmc2_set_buswidth_16(fmc2, true);
>  }
>  
> -void stm32_fmc2_write_data(struct nand_chip *chip, const void *buf,
> -			   unsigned int len, bool force_8bit)
> +static void stm32_fmc2_write_data(struct nand_chip *chip, const void *buf,
> +				  unsigned int len, bool force_8bit)
>  {
>  	struct stm32_fmc2_nfc *fmc2 = to_stm32_nfc(chip->controller);
>  	void __iomem *io_addr_w = fmc2->data_base[fmc2->cs_sel];
> @@ -1704,7 +1704,7 @@ static int stm32_fmc2_nand_ooblayout_free(struct mtd_info *mtd, int section,
>  	return 0;
>  }
>  
> -const struct mtd_ooblayout_ops stm32_fmc2_nand_ooblayout_ops = {
> +static const struct mtd_ooblayout_ops stm32_fmc2_nand_ooblayout_ops = {
>  	.ecc = stm32_fmc2_nand_ooblayout_ecc,
>  	.free = stm32_fmc2_nand_ooblayout_free,
>  };

This is nand/next material, so if you don't mind I would like to squash
this fix into the original commit inserting the driver.


Thanks,
Miquèl

  reply	other threads:[~2019-01-30 10:34 UTC|newest]

Thread overview: 12+ 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:09 ` YueHaibing
2019-01-30 10:09 ` YueHaibing
2019-01-30 10:34 ` Miquel Raynal [this message]
2019-01-30 10:34   ` Miquel Raynal
2019-01-30 10:34   ` Miquel Raynal
2019-01-30 10:43   ` YueHaibing
2019-01-30 10:43     ` YueHaibing
2019-01-30 10:43     ` YueHaibing
2019-02-05 19:06 ` Miquel Raynal
2019-02-05 19:06   ` Miquel Raynal
2019-02-05 19:06   ` Miquel Raynal

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=20190130113428.37570a55@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=alexandre.torgue@st.com \
    --cc=bbrezillon@kernel.org \
    --cc=christophe.kerello@st.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=marek.vasut@gmail.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=richard@nod.at \
    --cc=yuehaibing@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.