From: Josh Triplett <josh@joshtriplett.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (akpm-current tree related)
Date: Thu, 27 Feb 2014 17:29:10 -0800 [thread overview]
Message-ID: <20140228012907.GB9890@thin> (raw)
In-Reply-To: <20140227134057.6492e7e2bcbb592f71bef8d5@canb.auug.org.au>
On Thu, Feb 27, 2014 at 01:40:57PM +1100, Stephen Rothwell wrote:
> Hi Josh,
>
> On Wed, 26 Feb 2014 18:21:29 -0800 Josh Triplett <josh@joshtriplett.org> wrote:
> >
> > On Thu, Feb 27, 2014 at 10:00:26AM +1100, Stephen Rothwell wrote:
> > > Please check the build results overnight tonight (for next-20140227 at
> > > http://kisskb.ellerman.id.au/linux-next) and submit any more fixes for
> > > the allnoconfig build errors.
> >
> > Checking that site, I don't see any other instances of failures caused
> > by allnoconfig. If I'm missing some, could you please point me to the
> > page on that site I'm missing?
>
> That is because your patch was reverted in yesterday's (next-20140226)
> linux-next. You will need to look tomorrow (next-20140227) sometime.
It looks like the next-20140227 builds have shown up, and I only see one
additional allnoconfig build failure exposed by my patch (TTY dependency
on cris arch-v10). I sent a patch for that one.
I *think* that should have it covered; let me know if you see any
other failures.
- Josh Triplett
next prev parent reply other threads:[~2014-02-28 1:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 8:16 linux-next: build failure after merge of the final tree (akpm-current tree related) Stephen Rothwell
2014-02-26 10:02 ` Josh Triplett
2014-02-26 23:00 ` Stephen Rothwell
2014-02-26 23:17 ` Andrew Morton
2014-02-26 23:19 ` Josh Triplett
2014-02-26 23:42 ` Stephen Rothwell
2014-02-27 2:13 ` [PATCH] s390: select CONFIG_TTY for use of tty in unconditional keyboard driver Josh Triplett
2014-02-27 2:43 ` Stephen Rothwell
2014-02-27 7:07 ` Heiko Carstens
2014-02-28 1:27 ` [PATCH] cris: Make ETRAX_ARCH_V10 select TTY for use in debugport Josh Triplett
2014-02-28 2:30 ` Stephen Rothwell
2014-02-27 2:21 ` linux-next: build failure after merge of the final tree (akpm-current tree related) Josh Triplett
2014-02-27 2:40 ` Stephen Rothwell
2014-02-28 1:29 ` Josh Triplett [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-17 5:43 Stephen Rothwell
2013-08-16 7:16 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=20140228012907.GB9890@thin \
--to=josh@joshtriplett.org \
--cc=akpm@linux-foundation.org \
--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).