LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Alex Dewar <alex.dewar90@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	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: Mon, 14 Sep 2020 12:58:58 +0200	[thread overview]
Message-ID: <20200914125858.2614d92d@xps13> (raw)
In-Reply-To: <20200914095041.phuv6q7rl4nsdxnw@medion>

Hello,

Alex Dewar <alex.dewar90@gmail.com> wrote on Mon, 14 Sep 2020 10:50:41
+0100:

> On Mon, Sep 14, 2020 at 11:45:52AM +1000, Stephen Rothwell wrote:
> > Hi all,
> > 
> > After merging the nand tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> > 
> > drivers/mtd/nand/onenand/onenand_omap2.c:27:10: fatal error: asm/mach/flash.h: No such file or directory
> >    27 | #include <asm/mach/flash.h>
> >       |          ^~~~~~~~~~~~~~~~~~
> > 
> > Caused by commit
> > 
> >   26e1a8efc63d ("mtd: onenand: omap2: Allow for compile-testing on !ARM")
> > 
> > I have reverted that commit for today.
> 
> Gah, sorry :(. I definitely *tried* to build test it, but I must have
> messed up and built the wrong tree or something.
> 
> Apologies,
> Alex
> 
> > 
> > -- 
> > Cheers,
> > Stephen Rothwell
> 
> 

I'll drop this patch for now, we'll try to have it for the next release
if Alex fixes it.

Thanks,
Miquèl

  reply	other threads:[~2020-09-14 11:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14  1:45 linux-next: build failure after merge of the nand tree Stephen Rothwell
2020-09-14  9:50 ` Alex Dewar
2020-09-14 10: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-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=20200914125858.2614d92d@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=alex.dewar90@gmail.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).