From: Greg KH <gregkh@linuxfoundation.org>
To: "Sudarikov, Roman" <roman.sudarikov@linux.intel.com>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@redhat.com, namhyung@kernel.org,
linux-kernel@vger.kernel.org, eranian@google.com,
bgregg@netflix.com, ak@linux.intel.com,
kan.liang@linux.intel.com, alexander.antonov@intel.com
Subject: Re: [PATCH v7 0/3] perf x86: Exposing IO stack to IO PMON mapping through sysfs
Date: Tue, 18 Feb 2020 19:35:26 +0100 [thread overview]
Message-ID: <20200218183526.GB2665507@kroah.com> (raw)
In-Reply-To: <34ec945b-2456-7398-44c2-d523973e8e61@linux.intel.com>
On Tue, Feb 18, 2020 at 05:35:36PM +0300, Sudarikov, Roman wrote:
> Hi Greg,
>
> Could you please take a look at the patch set?
Could you please relax and wait? You sent this less than 48 hours ago:
> On 14.02.2020 17:01, roman.sudarikov@linux.intel.com wrote:
For a subsystem that I am not the maintainer of, and for a totally
low-priority issue, for a feature that I don't have hardware to test it
for.
You now have moved to the back of my pending review queue:
$ mdfrm -c ~/mail/todo/
437 messages in /home/gregkh/mail/todo/
As you well know, Intel is already on my "short list of companies to
ignore patches from" as it is, so I am going to force the issue now and
REQUIRE you to follow the internally documented Intel rules on how to
send patches to Greg. Hint, how you did it is _not_ how I have required
for it to happen. No idea how this snuck through my filters, I need to
go fix that up...
greg k-h
prev parent reply other threads:[~2020-02-18 18:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 14:01 roman.sudarikov
2020-02-14 14:01 ` [PATCH v7 1/3] perf x86: Infrastructure for exposing an Uncore unit to PMON mapping roman.sudarikov
2020-02-14 14:01 ` [PATCH v7 2/3] perf x86: Topology max dies for whole system roman.sudarikov
2020-02-14 14:01 ` [PATCH v7 3/3] perf x86: Exposing an Uncore unit to PMON for Intel Xeon® server platform roman.sudarikov
2020-02-18 14:35 ` [PATCH v7 0/3] perf x86: Exposing IO stack to IO PMON mapping through sysfs Sudarikov, Roman
2020-02-18 18:35 ` Greg KH [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=20200218183526.GB2665507@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.antonov@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bgregg@netflix.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=roman.sudarikov@linux.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
Powered by JetHome