From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
kyle@mcmartin.ca
Subject: Re: [GIT PULL] percpu for 2.6.31
Date: Fri, 19 Jun 2009 10:47:46 +0900 [thread overview]
Message-ID: <4A3AEE42.4010300@kernel.org> (raw)
In-Reply-To: <4A3AC0BA.4000407@kernel.org>
Hello, again.
Tejun Heo wrote:
> Oops, my apologies. I had them as floating series and apparently used
> different base commit when applying them. I did grep run and full yes
> build on the original quilt tree but didn't after quiltimport. Sorry.
I digged through git changelogs to find out where it went wrong. I
did use the same base commit when quiltimporting but when I updated
the patches on top of mainline two days ago, I forgot to quilt add the
file and the mce change got committed to the base tree instead of
quilt patch. After pulling the latest master into the quilt branch
yesterday, I updated the series for newcomers and everything worked
fine (as the base tree change got merged by git). quiltimporting of
course lost the base tree change and thinking the output gotta be
identical I didn't test the final git tree.
Anyways, I'm dropping the for-linus branch from percpu tree, fixing it
up, adding patchsets scheduled for .32 release and will try to get it
merged into #linux-next.
Thanks.
--
tejun
next prev parent reply other threads:[~2009-06-19 1:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 8:07 [GIT PULL] percpu for 2.6.31 Tejun Heo
2009-06-18 21:22 ` Linus Torvalds
2009-06-18 21:39 ` Andrew Morton
2009-06-18 22:43 ` Tejun Heo
2009-06-19 6:49 ` Ingo Molnar
2009-06-18 22:33 ` Tejun Heo
2009-06-18 22:45 ` Tejun Heo
2009-06-19 1:47 ` Tejun Heo [this message]
2009-06-19 5:39 ` Ingo Molnar
2009-06-19 19:39 ` Linus Torvalds
2009-06-19 21:08 ` Ingo Molnar
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=4A3AEE42.4010300@kernel.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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