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>
Subject: Re: linux-next: build failure after merge of the nand tree
Date: Fri, 11 Sep 2020 18:58:52 +0200 [thread overview]
Message-ID: <20200911185852.26a8a0a0@xps13> (raw)
In-Reply-To: <20200910141252.3faeb89b@canb.auug.org.au>
Hi Stephen,
Stephen Rothwell <sfr@canb.auug.org.au> wrote on Thu, 10 Sep 2020
14:12:52 +1000:
> Hi all,
>
> On Tue, 8 Sep 2020 13:35:36 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > After merging the nand tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> >
> > drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c: In function 'common_nfc_set_geometry':
> > drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c:513:33: error: 'chip' undeclared (first use in this function)
> > 513 | nanddev_get_ecc_requirements(&chip->base);
> > | ^~~~
> > drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c:513:33: note: each undeclared identifier is reported only once for each function it appears in
> >
> > Caused by commit
> >
> > aa5faaa5f95c ("mtd: rawnand: Use nanddev_get/set_ecc_requirements() when relevant")
> >
> > I have used the nand tree from next-20200903 for today.
>
> I am still getting this failure.
>
I am very sorry for all these errors, As usual, I pushed this branch to
my 0-day repository last Thursday and got a green light. But it
regularly happens, like this week, that I received an error report
even after that. This time the robot discovered the mistake at the
same time as you...
Anyway, it is now fixed and I pushed a hopefully fine nand/next branch.
As always, thank you very much for your time.
Miquèl
next prev parent reply other threads:[~2020-09-11 16:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 3:35 linux-next: build failure after merge of the nand tree Stephen Rothwell
2020-09-10 4:12 ` Stephen Rothwell
2020-09-11 16:58 ` Miquel Raynal [this message]
-- strict thread matches above, loose matches on Subject: below --
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-05-25 10:45 Stephen Rothwell
2020-05-25 11:54 ` Miquel Raynal
2020-05-12 4:08 Stephen Rothwell
2020-05-12 7:04 ` 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=20200911185852.26a8a0a0@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=boris.brezillon@collabora.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;
as well as URLs for NNTP newsgroup(s).