From: Ingo Molnar <mingo@kernel.org>
To: Christoph Lameter <cl@linux.com>
Cc: David Miller <davem@davemloft.net>,
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: Wed, 16 Oct 2013 12:37:51 +0200 [thread overview]
Message-ID: <20131016103751.GA24897@gmail.com> (raw)
In-Reply-To: <00000141b912103b-4bbb4dbd-747d-4a6d-8d1a-1a172eda4495-000000@email.amazonses.com>
* Christoph Lameter <cl@linux.com> wrote:
> > That won't cause email servers to reject the mails, it just makes the
> > patches a bit harder to review.
>
> I do not have any control over how my ISP sorts these emails. [...]
Your series from today has proper threading - so after all it _was_
possible for you to send a patch series correctly?
Note that you did not address the other problem that David Miller pointed
out, the Cc list still looks messed up:
Message-Id: <20131015180050.084352174@linux.com>
User-Agent: quilt/0.60-1
Date: Tue, 15 Oct 2013 12:58:53 -0500
From: Christoph Lameter <cl@linux.com>
To: Tejun Heo <tj@kernel.org>
Cc: akpm@linuxfoundation.org, "David S. Miller" <davem@davemloft.net>
Cc: linux-arch@vger.kernel.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>
Subject: [PATCH 01/10] net: Replace __get_cpu_var uses
Thanks,
Ingo
next prev parent reply other threads:[~2013-10-16 10:37 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
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 [this message]
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=20131016103751.GA24897@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