public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Boris Brezillon <boris.brezillon@collabora.com>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Christophe Kerello <christophe.kerello@st.com>
Subject: Re: linux-next: build failure after merge of the nand tree
Date: Tue, 12 May 2020 09:04:50 +0200	[thread overview]
Message-ID: <20200512090450.499421bd@xps13> (raw)
In-Reply-To: <20200512140840.0e102581@canb.auug.org.au>

Hi Stephen,

Stephen Rothwell <sfr@canb.auug.org.au> wrote on Tue, 12 May 2020
14:08:40 +1000:

> Hi all,
> 
> After merging the nand tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
> 
> drivers/mtd/nand/raw/stm32_fmc2_nand.c: In function 'stm32_fmc2_nfc_write_data':
> drivers/mtd/nand/raw/stm32_fmc2_nand.c:1294:34: error: 'fmc2' undeclared (first use in this function)
>  1294 |   stm32_fmc2_nfc_set_buswidth_16(fmc2, true);
>       |                                  ^~~~
> drivers/mtd/nand/raw/stm32_fmc2_nand.c:1294:34: note: each undeclared identifier is reported only once for each function it appears in
> 
> Caused by commit
> 
>   6c1c863ca431 ("mtd: rawnand: stm32_fmc2: cleanup")
> 
> I have used the nand tree from next-20200511 for today.
> 

Thanks for the notice, we will fix it by tomorrow.


Thanks,
Miquèl

  reply	other threads:[~2020-05-12  7:04 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12  4:08 linux-next: build failure after merge of the nand tree Stephen Rothwell
2020-05-12  7:04 ` Miquel Raynal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-04  2:28 Stephen Rothwell
2025-03-04 10:57 ` Miquel Raynal
2025-01-16  2:20 Stephen Rothwell
2025-01-17  2:23 ` Stephen Rothwell
2025-01-17  8:25   ` Miquel Raynal
2025-01-06  1:48 Stephen Rothwell
2025-01-06  1:51 ` Stephen Rothwell
2025-01-06  6:16   ` Md Sadre Alam
2025-01-06 13:23   ` Md Sadre Alam
2025-01-07  1:46     ` Stephen Rothwell
2023-08-21  2:02 Stephen Rothwell
2023-08-21  5:44 ` Md Sadre Alam
2022-09-21  1:32 Stephen Rothwell
2020-12-08  2:14 Stephen Rothwell
2020-09-14  1:45 Stephen Rothwell
2020-09-14  9:50 ` Alex Dewar
2020-09-14 10:58   ` Miquel Raynal
2020-09-08  3:35 Stephen Rothwell
2020-09-10  4:12 ` Stephen Rothwell
2020-09-11 16:58   ` Miquel Raynal
2020-05-25 10:45 Stephen Rothwell
2020-05-25 11:54 ` Miquel Raynal
2020-03-11  2:16 Stephen Rothwell
2020-03-11 10:10 ` Miquel Raynal
2020-03-11 14:01   ` Boris Brezillon
2020-03-11 19:20   ` Janusz Krzysztofik
2019-04-01 23:14 Stephen Rothwell
2019-04-01 23:31 ` Paul Cercueil
2019-04-02  7:27   ` Miquel Raynal
2019-04-02  9:21     ` Miquel Raynal
2019-04-02 11:56   ` Miquel Raynal
2019-04-02 12:00     ` Paul Cercueil
2019-04-02 12:16       ` 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=20200512090450.499421bd@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=boris.brezillon@collabora.com \
    --cc=christophe.kerello@st.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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