From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Christophe Kerello <christophe.kerello@st.com>
Cc: vigneshr@ti.com, bbrezillon@kernel.org, richard@nod.at,
linux-kernel@vger.kernel.org, marek.vasut@gmail.com,
linux-mtd@lists.infradead.org, computersforpeace@gmail.com,
dwmw2@infradead.org, linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH] mtd: rawnand: stm32_fmc2: avoid warnings when building with W=1 option
Date: Tue, 9 Jul 2019 09:59:25 +0200 [thread overview]
Message-ID: <20190709095925.7accd6f4@xps13> (raw)
In-Reply-To: <13d30ef8-b649-6416-3814-35a53c5c09ce@st.com>
Hi Christophe,
Christophe Kerello <christophe.kerello@st.com> wrote on Tue, 9 Jul 2019
09:50:10 +0200:
> On 7/1/19 9:11 AM, Miquel Raynal wrote:
> > Hi Christophe,
> >
> > Christophe Kerello <christophe.kerello@st.com> wrote on Fri, 21 Jun
> > 2019 16:43:09 +0200:
> >
> >> This patch solves warnings detected by setting W=1 when building.
> >>
> >> Warnings type detected:
> >> drivers/mtd/nand/raw/stm32_fmc2_nand.c: In function ‘stm32_fmc2_calc_timings’:
> >> drivers/mtd/nand/raw/stm32_fmc2_nand.c:1417:23: warning: comparison is
> >> always false due to limited range of data type [-Wtype-limits]
> >> else if (tims->twait > FMC2_PMEM_PATT_TIMING_MASK)
> >>
> >> Signed-off-by: Christophe Kerello <christophe.kerello@st.com>
> >> ---
> >
> > Applied to nand/next, thanks.
>
> Hi Miquel,
>
> After fetching nand/next, I do not see this patch applied.
>
Not sure what happened, please resend with a Fixes/stable tag added,
I'll apply when -rc1 will be out.
Sorry again for the trouble, thanks for the notice!
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2019-07-09 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 14:43 [PATCH] mtd: rawnand: stm32_fmc2: avoid warnings when building with W=1 option Christophe Kerello
2019-07-01 7:11 ` Miquel Raynal
2019-07-09 7:50 ` Christophe Kerello
2019-07-09 7:59 ` 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=20190709095925.7accd6f4@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=bbrezillon@kernel.org \
--cc=christophe.kerello@st.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@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=richard@nod.at \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).