From: Stephen Rothwell <sfr@canb.auug.org.au>
To: 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>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>
Subject: linux-next: build failure after merge of the mtd-fixes tree
Date: Mon, 18 May 2020 08:40:21 +1000 [thread overview]
Message-ID: <20200518084021.64cbf411@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 868 bytes --]
Hi all,
After merging the mtd-fixes tree, today's linux-next build (x86_64
allmodconfig) failed like this:
/home/sfr/next/next/drivers/mtd/nand/spi/core.c: In function 'spinand_init':
/home/sfr/next/next/drivers/mtd/nand/spi/core.c:1093:26: error: 'struct nand_device' has no member named 'ecc'
1093 | mtd->ecc_strength = nand->ecc.ctx.conf.strength;
| ^~
/home/sfr/next/next/drivers/mtd/nand/spi/core.c:1094:27: error: 'struct nand_device' has no member named 'ecc'
1094 | mtd->ecc_step_size = nand->ecc.ctx.conf.step_size;
| ^~
Caused by commit
d5baa0ec83de ("mtd: spinand: Propagate ECC information to the MTD structure")
"This fix depends on recent changes and should not be backported as-is." ?
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-05-17 22:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 22:40 Stephen Rothwell [this message]
2020-05-17 23:02 ` linux-next: build failure after merge of the mtd-fixes tree Richard Weinberger
2020-05-18 7:45 ` 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=20200518084021.64cbf411@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=richard@nod.at \
/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