From: Tejun Heo <tj@kernel.org>
To: Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Rusty Russell <rusty@rustcorp.com.au>,
x86@kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: #tj-percpu has been rebased
Date: Sat, 31 Jan 2009 02:05:20 +0900 [thread overview]
Message-ID: <49833350.1020809@kernel.org> (raw)
Hello,
tj-percpu has been rebased. Sorry, the previous tree was discarded
because it was missing several patches in the middle but rebasing on
top of new misc/tj-percpu shouldn't be too difficult. What have
happened are...
* Rebased on top of the current 2.6/master[1].
* hardirq unification patches restored.
* linker bug fix and xen fix patches applied.
* misc/tj-cpus4096 created as tip/cpus4096 + uv_flush_tlb_others()
cleanup patch (w/ Cliff Wickman's fixes folded in) and got merged
into misc/tj-percpu.
* misc/tj-stackprotector created as tip/stackprotector^ + three
patches. The back tracked commit is merge with the previous
core/percpu. misc/tj-stackprotector got merged into misc/tj-percpu.
So, all in all, the rebase is complete. No patch is lost but on
hindsight it should really have been done by pulling in 2.6/master.
The end result is the same anyway sans slightly simpler merge tree and
it definitely doesn't feel like it's worth the trouble. Well, what's
done is done. Please keep sending patches.
The git vector is as always...
git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git tj-percpu
Thanks.
--
tejun
[1] f2257b70b0f9b2fe8f2afd83fc6798dca75930b8
next reply other threads:[~2009-01-30 17:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 17:05 Tejun Heo [this message]
2009-01-31 5:46 ` #tj-percpu has been rebased Tejun Heo
2009-01-31 13:28 ` Ingo Molnar
2009-02-02 9:04 ` Rusty Russell
2009-02-04 3:18 ` Tejun Heo
2009-02-12 3:37 ` Tejun Heo
2009-02-12 3:44 ` Tejun Heo
2009-02-13 20:58 ` Rusty Russell
2009-02-13 21:17 ` Jeremy Fitzhardinge
2009-02-13 22:59 ` H. Peter Anvin
2009-02-14 0:45 ` Tejun Heo
2009-02-14 1:53 ` H. Peter Anvin
2009-02-14 2:10 ` Tejun Heo
2009-02-16 7:23 ` Rusty Russell
2009-02-16 17:28 ` H. Peter Anvin
2009-02-16 23:22 ` Rusty Russell
2009-02-16 23:28 ` H. Peter Anvin
2009-02-18 4:25 ` Rusty Russell
2009-02-18 6:40 ` H. Peter Anvin
2009-02-18 7:11 ` Rusty Russell
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=49833350.1020809@kernel.org \
--to=tj@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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