From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
Boris Brezillon <boris.brezillon@collabora.com>
Cc: 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: Thu, 10 Sep 2020 14:12:52 +1000 [thread overview]
Message-ID: <20200910141252.3faeb89b@canb.auug.org.au> (raw)
In-Reply-To: <20200908133536.6ab7a7f0@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 892 bytes --]
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.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-09-10 4:13 UTC|newest]
Thread overview: 35+ 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 [this message]
2020-09-11 16:58 ` Miquel Raynal
-- 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-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=20200910141252.3faeb89b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=boris.brezillon@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=miquel.raynal@bootlin.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