From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andy Lutomirski <luto@amacapital•net>
Cc: "linux-next@vger•kernel.org" <linux-next@vger•kernel.org>,
"Paul E. McKenney" <paulmck@linux•vnet.ibm.com>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: question about the luto-misc tree
Date: Sun, 14 Dec 2014 23:04:45 +1100 [thread overview]
Message-ID: <20141214230445.7caf202b@canb.auug.org.au> (raw)
In-Reply-To: <CALCETrXu19aHhudTfPAr5PM05FR0xKBiSHgbubVhh6QUrHCADw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]
Hi Andy,
On Sat, 13 Dec 2014 23:26:36 -0800 Andy Lutomirski <luto@amacapital•net> wrote:
>
> On Dec 13, 2014 10:58 PM, "Stephen Rothwell" <sfr@canb•auug.org.au> wrote:
> >
> > The luto-misc tree seems to have a whole series of commits in it that
> > have just bee removed from the rcu tree ... You really have to be very
> > careful if you base your work on a tree that is regularly rebased.
>
> Hmm. They were there a couple days ago. Paul, what should I do about
> this? I only need the one NMI nesting change for the stuff in
> luto/next.
One of them was causing a problem and (I think) the rest were for v3.20
and so Paul reset his tree.
> > I also wonder if the other commits in that tree are destined for
> > v3.19? If they are for v3.20, then they should not be in linux-next
> > until after v3.19-rc1 has been released.
>
> They're for 3.20. I'll drop the whole series from the next branch for now.
Thanks.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-12-14 12:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-14 6:57 linux-next: question about the luto-misc tree Stephen Rothwell
2014-12-14 7:26 ` Andy Lutomirski
2014-12-14 12:03 ` Paul E. McKenney
2014-12-14 16:29 ` Andy Lutomirski
2014-12-14 17:37 ` Paul E. McKenney
2014-12-14 17:41 ` Andy Lutomirski
2014-12-14 18:17 ` Paul E. McKenney
2014-12-22 19:16 ` Andy Lutomirski
2014-12-26 1:33 ` Stephen Rothwell
2014-12-26 17:02 ` Paul E. McKenney
2014-12-28 18:17 ` Andy Lutomirski
[not found] ` <CALCETrWaT019BZoyhp-CkcCiEXYEumvjF2pA6GHk0Mo-sPngTQ@mail.gmail.com>
2014-12-31 13:16 ` Paul E. McKenney
2014-12-14 12:04 ` Stephen Rothwell [this message]
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=20141214230445.7caf202b@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=luto@amacapital$(echo .)net \
--cc=paulmck@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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