From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Graham Moore <grmoore@opensource.altera.com>,
Marek Vasut <marex@denx.de>
Subject: Re: linux-next: build failure after merge of the l2-mtd tree
Date: Tue, 19 Jul 2016 11:46:22 +1000 [thread overview]
Message-ID: <20160719114622.577185f5@canb.auug.org.au> (raw)
In-Reply-To: <20160719012039.GA18583@google.com>
Hi Brian,
On Mon, 18 Jul 2016 18:20:39 -0700 Brian Norris <computersforpeace@gmail.com> wrote:
>
> Known:
>
> http://lists.infradead.org/pipermail/linux-mtd/2016-July/068569.html
>
> > Missing include of linux/io.h ...
>
> It's not missing linux/io.h; x86 is missing readsl()/writesl(). If x86
> folks don't have a solution, then I guess we'll just make this depend on
> !X86.
or remove COMPILE_TEST if it can't compile for everyone ...
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2016-07-19 1:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 0:59 linux-next: build failure after merge of the l2-mtd tree Stephen Rothwell
2016-07-19 1:20 ` Brian Norris
2016-07-19 1:46 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-28 2:19 Stephen Rothwell
2017-08-28 22:06 ` Brian Norris
2017-02-09 1:08 Stephen Rothwell
2017-02-09 1:59 ` Brian Norris
2015-12-21 5:47 Stephen Rothwell
2015-09-30 5:16 Stephen Rothwell
2014-05-22 5:30 Stephen Rothwell
2014-05-26 17:42 ` Brian Norris
2014-05-26 23:59 ` Stephen Rothwell
2014-05-27 10:40 ` Artem Bityutskiy
2014-05-27 22:49 ` Stephen Rothwell
2012-10-12 0:14 Stephen Rothwell
2012-10-12 4:51 ` Dinh Nguyen
2012-10-18 0:28 ` Stephen Rothwell
2012-10-18 9:26 ` Artem Bityutskiy
2012-02-07 2:58 Stephen Rothwell
2012-02-07 8:02 ` Artem Bityutskiy
2012-02-06 1:07 Stephen Rothwell
2012-02-06 9:14 ` Artem Bityutskiy
2012-02-06 21:10 ` Stephen Rothwell
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=20160719114622.577185f5@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=computersforpeace@gmail.com \
--cc=grmoore@opensource.altera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marex@denx.de \
/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).