From: Ingo Molnar <mingo@kernel.org>
To: David Miller <davem@davemloft.net>
Cc: cl@linux.com, tj@kernel.org, akpm@linuxfoundation.org,
srostedt@redhat.com, linux-kernel@vger.kernel.org,
peterz@infradead.org, tglx@linutronix.de
Subject: Re: [PATCH 0/6] percpu: Implement Preemption checks for __this_cpu operations V4
Date: Sat, 12 Oct 2013 18:51:20 +0200 [thread overview]
Message-ID: <20131012165120.GA15116@gmail.com> (raw)
In-Reply-To: <20131011.140814.422793173894221852.davem@davemloft.net>
* David Miller <davem@davemloft.net> wrote:
> Most sites are rejecting your posting because the CC: list looked like
> this:
>
> Cc: akpm@linuxfoundation.org
> Cc: Steven Rostedt <srostedt@redhat.com>
> Cc: linux-kernel@vger.kernel.org
> Cc: Ingo Molnar <mingo@kernel.org>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
>
> Please only specify one CC: list with a comma separated list of
> recipients.
Another problem is that the patch emails are not properly threaded to the
0/6 patch and thus appear out of order and mixed up:
66216 N C Oct 11 Christoph Lamet ( 36) [PATCH 0/6] percpu: Implement Preemption checks for __this_cpu operations V4
66217 N C Oct 11 David Miller ( 13) └─>
66218 N C Oct 11 Christoph Lamet ( 43) ┬─>[PATCH 1/6] net: ip4_datagram_connect: Use correct form of statistics update
66219 N C Oct 11 Eric Dumazet ( 17) │ └─>
66220 N C Oct 11 Christoph Lamet ( 121) ├─>[PATCH 2/6] percpu: Add raw_cpu_ops
66221 N C Oct 11 Christoph Lamet ( 189) ├─>[PATCH 6/6] percpu: Add preemption checks to __this_cpu ops
66222 N C Oct 11 Christoph Lamet ( 64) ├─>[PATCH 5/6] net: __this_cpu_inc in route.c
66223 N C Oct 11 Christoph Lamet ( 103) ├─>[PATCH 3/6] mm: Use raw_cpu ops for determining current NUMA node
66224 N C Oct 11 Christoph Lamet ( 43) └─>[PATCH 4/6] Use raw_cpu_write for initialization of per cpu refcount.
Note how the order is 1,2,6,5,3,4 with no threading instead of 1,2,3,4,5,6
with proper threading.
That won't cause email servers to reject the mails, it just makes the
patches a bit harder to review.
Most kernel developers tend to use 'git send-email' to send patches to
lkml, and that method is working pretty reliably.
The relevant 'git send-email' line is pretty well described in Greg's "The
newbie's guide to hacking the Linux kernel" book:
http://www.tuxradar.com/content/newbies-guide-hacking-linux-kernel
Thanks,
Ingo
next prev parent reply other threads:[~2013-10-12 16:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 17:54 [PATCH 0/6] percpu: Implement Preemption checks for __this_cpu operations V4 Christoph Lameter
2013-10-11 18:08 ` David Miller
2013-10-12 16:51 ` Ingo Molnar [this message]
2013-10-14 10:32 ` Peter Zijlstra
2013-10-14 19:02 ` Christoph Lameter
2013-10-15 8:23 ` Peter Zijlstra
2013-10-14 22:24 ` Christoph Lameter
2013-10-15 7:07 ` Ingo Molnar
2013-10-16 10:37 ` Ingo Molnar
2013-10-16 14:32 ` Christoph Lameter
2013-10-14 13:09 ` Steven Rostedt
2013-10-14 19:03 ` Christoph Lameter
-- strict thread matches above, loose matches on Subject: below --
2013-10-11 16:52 Christoph Lameter
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=20131012165120.GA15116@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linuxfoundation.org \
--cc=cl@linux.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=srostedt@redhat.com \
--cc=tglx@linutronix.de \
--cc=tj@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