[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130119055501.GA2802@ZenIV.linux.org.uk>
Date: Sat, 19 Jan 2013 05:55:01 +0000
From: Al Viro <viro@...IV.linux.org.uk>
To: James Hogan <james.hogan@...tec.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org
Subject: Re: [PATCH v3 00/44] Meta Linux Kernel Port
On Sat, Jan 12, 2013 at 09:55:07AM +0000, James Hogan wrote:
> Hi Stephen, Al,
>
> On Sat, Jan 12, 2013 at 12:09:57PM +1100, Stephen Rothwell wrote:
> > On Fri, 11 Jan 2013 15:02:06 +0000 James Hogan <james.hogan@...tec.com> wrote:
> > >
> > > Okay, I've rebased the metag tree from linux-next onto the master branch
> > > of Al's signal tree (to get Vineet's GENERIC_SIGALTSTACK fix and
> > > GENERIC_SIGALTSTACK's eventual removal).
> >
> > OK, but I hope you mentioned not rebasing to Al.
>
> I'm still rebasing the metag tree, and it's not quite ready for -next so
> I don't mind if Al's tree rebases at this stage tbh.
>
> Al: I don't know if you normally rebase your tree, but if it's okay with
> you I'll let you know when I need it not to be rebased.
Umm...
1) #master is definitely bad for base; #for-linus is much safer (and
sufficient for your case)
2) I'm a couple of fix folds away from opening #no-rebase (and yes,
it'll be a superset of #for-linus)
FWIW, I'd suggest a rebase on top of signal.git#for-linus. Noting in
the stem is visibly relevant in your case, AFAICS...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists