From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jiri Kosina <jkosina@suse.cz>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Temporary -rcu tree location
Date: Tue, 13 Sep 2011 09:06:45 -0700 [thread overview]
Message-ID: <20110913160645.GA6258@linux.vnet.ibm.com> (raw)
In-Reply-To: <20110913040647.GC2313@linux.vnet.ibm.com>
On Mon, Sep 12, 2011 at 09:06:47PM -0700, Paul E. McKenney wrote:
> On Tue, Sep 13, 2011 at 12:07:16PM +1000, Stephen Rothwell wrote:
> > Hi Paul,
> >
> > On Mon, 12 Sep 2011 18:34:00 -0700 "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
> > >
> > > > there doesn't seem to be 'rcu/next' branch, right?
> > >
> > > No, there is not. So the idea is to push "rcu/next" the first time,
> > > then ":rcu/next" thereafter?
> >
> > Can't you just do a (forced) push over and over again without removing
> > the branch each time?
>
> I will give it a try on the next update. ;-)
OK, I pushed a small update to one of the commits, this time to branch
rcu/next, again at https://github.com/paulmckrcu/linux.
I guess that the acid test is the next time I update. ;-)
Thanx, Paul
next prev parent reply other threads:[~2011-09-13 16:24 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 [this message]
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
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=20110913160645.GA6258@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=jkosina@suse.cz \
--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.