From: Alex Shi <alex.shi@intel.com>
To: linux-kernel@vger.kernel.org, cl@gentwo.org,
eric.dumazet@gmail.com, tglx@linutronix.de, avi@redhat.com,
akpm@linux-foundation.org, davem@davemloft.net, kaber@trash.net,
a.p.zijlstra@chello.nl, ying.huang@intel.com,
konrad.wilk@oracle.com, hpa@zytor.com, jeremy@goop.org
Subject: [PATH v2 0/5] Code clean up for percpu_xxx serial functions
Date: Fri, 13 Jan 2012 23:53:33 +0800 [thread overview]
Message-ID: <1326470018-22342-1-git-send-email-alex.shi@intel.com> (raw)
I am sorry for spelling mistaken on konrad's email address, so resend
for correct this. Please reply this resend email.
---------------
Thanks for TJ's suggestion, I split the serial patch smaller for
potential bisection convenience.
Compare to v1 patch, this v2 patches has separate function replace
patches and final dead code clean up patch.
The net, xen and x86 part code are independent.
After each part was accepted in kernel, the final(5th) clean up code
do the real clean up in next merge window. I will refresh the patch
at that time.
Any further comments are appreciated!
Regards
Alex
next reply other threads:[~2012-01-13 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 15:53 Alex Shi [this message]
2012-01-13 15:53 ` [PATCH v2 1/5] net: use this_cpu_xxx replace percpu_xxx funcs Alex Shi
2012-01-13 15:53 ` [PATCH v2 2/5] xen: " Alex Shi
2012-01-13 15:53 ` [PATCH v2 3/5] x86: " Alex Shi
2012-01-13 15:53 ` [PATCH v2 4/5] x86: change percpu_read_stable to this_cpu_read_stable Alex Shi
2012-01-13 15:53 ` [PATCH v2 5/5] x86: Code clean up for percpu_xxx() functions Alex Shi
2012-05-04 21:29 ` [PATH v2 0/5] Code clean up for percpu_xxx serial functions Andrew Morton
2012-05-05 1:09 ` Alex Shi
-- strict thread matches above, loose matches on Subject: below --
2012-01-13 15:45 Alex Shi
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=1326470018-22342-1-git-send-email-alex.shi@intel.com \
--to=alex.shi@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=cl@gentwo.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=kaber@trash.net \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=ying.huang@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).