[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20121217141355.9bbbd1ef4c59959bf7940a4a@canb.auug.org.au>
Date: Mon, 17 Dec 2012 14:13:55 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Chris Mason <chris.mason@...ionio.com>
Cc: Chris Mason <clmason@...ionio.com>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Stefan Behrens <sbehrens@...ntdisaster.de>,
Josef Bacik <JBacik@...ionio.com>,
Linus <torvalds@...ux-foundation.org>
Subject: Re: linux-next: build failure after merge of the btrfs tree
Hi Chris,
On Sun, 16 Dec 2012 21:52:41 -0500 Chris Mason <chris.mason@...ionio.com> wrote:
>
> On Sun, Dec 16, 2012 at 05:15:04PM -0700, Chris Mason wrote:
> > On Sun, Dec 16, 2012 at 04:00:22PM -0700, Stephen Rothwell wrote:
> > Josef and I have sob on all of our commits (at least all the ones not in
> > 3.7, I didn't go back farther). In this case the Author was Stefan and
> > it ended up rebased in either Josef's or my tree. We usually try to
> > preserve merges on rebase, but this time was a bigger set of changes
> > than usual and it didn't work out.
>
> Just FYI, I've pushed out a fixed version of the tree with proper
> signed-off-by on all the commits, thanks for catching that.
>
> It also has the fix for the ppc compile problems. (This isn't a pull
> request yet, I've got the hash collision fix and a few others pending as
> well).
You do realise that I just fetch your tree/branch each day, right? So it
will be in tomorrow's linux-next.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists