From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Christoph Lameter <cl@linux.com>, Tejun Heo <tj@kernel.org>,
akpm@linuxfoundation.org, Steven Rostedt <srostedt@redhat.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [pchecks v2 0/2] percpu v3: Implement Preemption checks for __this_cpu operations
Date: Fri, 4 Oct 2013 10:30:33 +0200 [thread overview]
Message-ID: <20131004083033.GA1658@gmail.com> (raw)
In-Reply-To: <20131004081807.GF3081@twins.programming.kicks-ass.net>
* Peter Zijlstra <peterz@infradead.org> wrote:
> User-Agent: quilt/0.50-1
>
> You might want to upgrade your quilt the latest version is 0.60-1 and
> there's talk of actually releasing something newer.
Another technical problem with the submission is the lack of 'PATCH' tags
for the patches - it's the standard and ther are folks search lkml based
on that pattern.
See Documentation/SubmittingPatches:
| 11) Include PATCH in the subject
|
| Due to high e-mail traffic to Linus, and to linux-kernel, it is common
| convention to prefix your subject line with [PATCH]. This lets Linus
| and other kernel developers more easily distinguish patches from other
| e-mail discussions.
Note that all of the technical problems we noted need to be fixed before
the next resubmission, not just some.
Thanks,
Ingo
prev parent reply other threads:[~2013-10-04 8:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 18:28 [pchecks v2 0/2] percpu v3: Implement Preemption checks for __this_cpu operations Christoph Lameter
2013-10-04 6:01 ` Ingo Molnar
2013-10-04 8:18 ` Peter Zijlstra
2013-10-04 8:30 ` Ingo Molnar [this message]
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=20131004083033.GA1658@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linuxfoundation.org \
--cc=cl@linux.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.