From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
David Miller <davem@davemloft.net>, Meelis Roos <mroos@linux.ee>
Subject: Re: [GIT PULL] percpu fixes for 2.6.31-rc8
Date: Tue, 01 Sep 2009 21:56:56 +0900 [thread overview]
Message-ID: <4A9D1A18.5000201@kernel.org> (raw)
In-Reply-To: <4A9D18B7.3010405@kernel.org>
Tejun Heo wrote:
> Hello, Linus.
>
> Please consider pulling from the following percpu fixes tree.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/percpu.git for-linus
Ummm... one question. The above tree is on top of the previous
for-linus fixes tree. It pulls in to the current #master alright but
it would still be a merge instead of a fast-forward. Would it be
better to prep fixes tree on top of the current #master so that it
results in fast-forward? If that's the case, please let me know or
just cherry pick the top commit.
Thanks.
--
tejun
next prev parent reply other threads:[~2009-09-01 12:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 12:51 [GIT PULL] percpu fixes for 2.6.31-rc8 Tejun Heo
2009-09-01 12:56 ` Tejun Heo [this message]
2009-09-05 21:23 ` Linus Torvalds
2009-09-05 21:44 ` Tejun Heo
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=4A9D1A18.5000201@kernel.org \
--to=tj@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox