[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130821102246.4e3c4c8fe549d8c7760da96d@canb.auug.org.au>
Date: Wed, 21 Aug 2013 10:22:46 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Ben Myers <bpm@....com>
Cc: Dwight Engen <dwight.engen@...cle.com>,
Jeremy Kerr <jk@...abs.org>, cbe-oss-dev@...ts.ozlabs.org,
Arnd Bergmann <arnd@...db.de>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
linux-kernel@...r.kernel.org, xfs@....sgi.com,
linux-next@...r.kernel.org, Gao feng <gaofeng@...fujitsu.com>,
linuxppc-dev@...ts.ozlabs.org
Subject: Re: linux-next: build failure after merge of the final tree
Hi Ben,
On Tue, 20 Aug 2013 14:28:44 -0500 Ben Myers <bpm@....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). This does need to be fixed fairly soon, though.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists