LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
Boris Brezillon <boris.brezillon@collabora.com>
Cc: Valentin Korenblit <vkorenblit@sequans.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the nand tree
Date: Wed, 21 Sep 2022 11:32:25 +1000 [thread overview]
Message-ID: <20220921113225.2f45ba3b@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]
Hi all,
After merging the nand tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/mtd/nand/raw/cadence-nand-controller.c: In function 'cadence_nand_read_buf':
drivers/mtd/nand/raw/cadence-nand-controller.c:1893:25: error: implicit declaration of function 'ioread64_rep'; did you mean 'ioread32_rep'? [-Werror=implicit-function-declaration]
1893 | ioread64_rep(cdns_ctrl->io.virt, buf, len_in_words);
| ^~~~~~~~~~~~
| ioread32_rep
drivers/mtd/nand/raw/cadence-nand-controller.c: In function 'cadence_nand_write_buf':
drivers/mtd/nand/raw/cadence-nand-controller.c:1962:25: error: implicit declaration of function 'iowrite64_rep'; did you mean 'iowrite32_rep'? [-Werror=implicit-function-declaration]
1962 | iowrite64_rep(cdns_ctrl->io.virt, buf, len_in_words);
| ^~~~~~~~~~~~~
| iowrite32_rep
Caused by commit
7e7dc04774b1 ("mtd: rawnand: cadence: support 64-bit slave dma interface")
I have used the nand tree from next-20220920 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-09-21 1:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 1:32 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-21 2:02 linux-next: build failure after merge of the nand tree Stephen Rothwell
2023-08-21 5:44 ` Md Sadre Alam
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-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=20220921113225.2f45ba3b@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 \
--cc=vkorenblit@sequans.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).