From: Ben Myers <bpm@sgi.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: cbe-oss-dev@lists.ozlabs.org, Arnd Bergmann <arnd@arndb.de>,
Dwight Engen <dwight.engen@oracle.com>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com,
linux-next@vger.kernel.org, Jeremy Kerr <jk@ozlabs.org>,
linuxppc-dev@lists.ozlabs.org, Gao feng <gaofeng@cn.fujitsu.com>
Subject: Re: linux-next: build failure after merge of the final tree
Date: Wed, 21 Aug 2013 10:54:16 -0500 [thread overview]
Message-ID: <20130821155416.GH5262@sgi.com> (raw)
In-Reply-To: <20130821102246.4e3c4c8fe549d8c7760da96d@canb.auug.org.au>
Hey Stephen,
On Wed, Aug 21, 2013 at 10:22:46AM +1000, Stephen Rothwell wrote:
> On Tue, 20 Aug 2013 14:28:44 -0500 Ben Myers <bpm@sgi.com> wrote:
> > I'd prefer not to break Stephen's tree two days in a row. We could just revert
> > d6970d4b726c in the xfs tree for the time being as Stephen has done, but given
> > the choice would prefer the fix. Do you have a preference between the two
> > approaches that Dwight has posted? The first seems more conservative...
>
> I will automatically revert that commit when I merge the xfs tree until
> some other solution is forthcoming (so you don't have to do the revert in
> the xfs tree).
Gah. That makes sense. ;)
> This does need to be fixed fairly soon, though.
Agreed, thanks.
-Ben
next prev parent reply other threads:[~2013-08-21 15:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 7:20 linux-next: build failure after merge of the final tree Stephen Rothwell
2013-08-20 16:07 ` Dwight Engen
2013-08-20 19:28 ` Ben Myers
2013-08-21 0:22 ` Stephen Rothwell
2013-08-21 15:54 ` Ben Myers [this message]
2013-08-20 20:46 ` Arnd Bergmann
2013-08-21 5:08 ` Dwight Engen
2013-08-21 6:30 ` Jeremy Kerr
2013-08-21 15:56 ` Ben Myers
2013-08-21 18:33 ` [PATCH] powerpc/spufs: convert userns uid/gid mount options to kuid/kgid Dwight Engen
2013-08-21 20:05 ` Arnd Bergmann
2013-08-21 20:24 ` Ben Myers
-- strict thread matches above, loose matches on Subject: below --
2014-01-06 9:28 linux-next: build failure after merge of the final tree Stephen Rothwell
2014-01-06 23:12 ` Benjamin Herrenschmidt
2012-07-05 8:33 Stephen Rothwell
2012-07-05 9:43 ` Alan Modra
2012-07-06 0:21 ` Stephen Rothwell
2012-07-06 0:57 ` Alan Modra
2012-07-06 3:01 ` Stephen Rothwell
2012-07-06 6:08 ` Alan Modra
2012-02-27 6:37 Stephen Rothwell
2012-02-27 9:19 ` Benjamin Herrenschmidt
2012-02-27 23:30 ` Benjamin Herrenschmidt
2012-01-20 7:21 Stephen Rothwell
2012-01-20 9:08 ` Deepthi Dharwar
2011-07-18 9:35 Stephen Rothwell
2011-01-31 6:26 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=20130821155416.GH5262@sgi.com \
--to=bpm@sgi.com \
--cc=arnd@arndb.de \
--cc=cbe-oss-dev@lists.ozlabs.org \
--cc=dwight.engen@oracle.com \
--cc=gaofeng@cn.fujitsu.com \
--cc=jk@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sfr@canb.auug.org.au \
--cc=xfs@oss.sgi.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).