From: zhouchengming <zhouchengming1@huawei.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: <linux-kernel@vger.kernel.org>, <x86@kernel.org>,
<mingo@redhat.com>, <peterz@infradead.org>, <hpa@zytor.com>,
<ak@linux.intel.com>, <eranian@google.com>, <kan.liang@intel.com>,
<davidcc@google.com>, <dave.hansen@linux.intel.com>,
<qiaonuohan@huawei.com>, <guohanjun@huawei.com>
Subject: Re: [PATCH] fix race caused by hyperthreads when online an offline cpu
Date: Mon, 16 Jan 2017 17:53:16 +0800 [thread overview]
Message-ID: <587C980C.3090300@huawei.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1701161003200.3877@nanos>
On 2017/1/16 17:05, Thomas Gleixner wrote:
> On Mon, 16 Jan 2017, Zhou Chengming wrote:
>
> Can you please stop sending the same patch over and over every other day?
>
> Granted, things get forgotten, but sending a polite reminder after a week
> is definitely enough.
>
> Maintainers are not machines responding within a split second on every mail
> they get. And that patch is not so substantial that it justifies that kind
> of spam.
>
Very sorry for the noise. We are just not sure this is the right fix because it's
hard to reproduce.
Thanks.
> Thanks,
>
> tglx
>
>
>
> .
>
next prev parent reply other threads:[~2017-01-16 9:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 3:21 [PATCH] fix race caused by hyperthreads when online an offline cpu Zhou Chengming
2017-01-16 9:05 ` Thomas Gleixner
2017-01-16 9:53 ` zhouchengming [this message]
2017-01-16 18:36 ` Stephane Eranian
2017-01-17 10:05 ` Thomas Gleixner
2017-01-17 10:12 ` [tip:perf/urgent] perf/x86/intel: Handle exclusive threadid correctly on CPU hotplug tip-bot for Zhou Chengming
-- strict thread matches above, loose matches on Subject: below --
2017-01-14 11:21 [PATCH] fix race caused by hyperthreads when online an offline cpu Zhou Chengming
2017-01-12 9:32 Zhou Chengming
2017-01-14 1:33 ` qiaonuohan
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=587C980C.3090300@huawei.com \
--to=zhouchengming1@huawei.com \
--cc=ak@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=davidcc@google.com \
--cc=eranian@google.com \
--cc=guohanjun@huawei.com \
--cc=hpa@zytor.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=qiaonuohan@huawei.com \
--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 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.