From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Temporary -rcu tree location
Date: Mon, 12 Sep 2011 18:32:43 -0700 [thread overview]
Message-ID: <20110913013243.GA2313@linux.vnet.ibm.com> (raw)
In-Reply-To: <20110913112127.cd62b006c302a575ceae4dee@canb.auug.org.au>
On Tue, Sep 13, 2011 at 11:21:27AM +1000, Stephen Rothwell wrote:
> Hi Paul,
>
> On Mon, 12 Sep 2011 17:01:07 -0700 "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
> >
> > Could you please make the -next tree pull from branch next.2011.09.12a
> > of https://github.com/paulmckrcu/linux while kernel.org is down?
>
> I have swiched to that now (actually git://github.com/paulmckrcu/linux).
> Just a couple of minor changes and some new commits, right? Hash of the
> branch top commit is f88a19a.
Yep, that is the one! And yes, not hugely different than the last
rcu/next from the kernel.org -rcu, but Linus seemed to be rather serious
about pull requests having been exposed to -next testing. ;-)
Thanx, Paul
prev parent reply other threads:[~2011-09-13 1:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 0:01 Temporary -rcu tree location Paul E. McKenney
2011-09-13 0:11 ` Jiri Kosina
2011-09-13 0:24 ` Paul E. McKenney
2011-09-13 0:43 ` Jiri Kosina
2011-09-13 1:34 ` Paul E. McKenney
2011-09-13 2:07 ` Stephen Rothwell
2011-09-13 4:06 ` Paul E. McKenney
2011-09-13 16:06 ` Paul E. McKenney
2011-09-14 0:20 ` Stephen Rothwell
2011-09-13 0:47 ` Stephen Rothwell
2011-09-13 1:14 ` Stephen Rothwell
2011-09-13 1:21 ` Stephen Rothwell
2011-09-13 1:32 ` Paul E. McKenney [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=20110913013243.GA2313@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.