From: Greg KH <gregkh@linuxfoundation.org>
To: Felix Schnizlein <fschnizlein@suse.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
yanmin.zhang@intel.com, trenn@suse.com, mingo@redhat.com
Subject: Re: [RFC PATCHv2 2/2] Implement sysfs based cpuinfo for x86 cpus.
Date: Wed, 14 Jun 2017 17:04:10 +0200 [thread overview]
Message-ID: <20170614150410.GA15806@kroah.com> (raw)
In-Reply-To: <1497450781-52354-3-git-send-email-fschnizlein@suse.com>
On Wed, Jun 14, 2017 at 04:33:01PM +0200, Felix Schnizlein wrote:
> Signed-off-by: Felix Schnizlein <fschnizlein@suse.com>
> Signed-off-by: Thomas Renninger <trenn@suse.com>
> ---
I know I reject flat-out any patch without a changelog text.
And you NEVER can add a whole new feature without any text here at all,
that's just crazy...
Also, I almost never review RFC patches, as obviously the submitter
doesn't think they are ready to be merged, so why should I review them
just yet? :)
thanks,
greg k-h
parent reply other threads:[~2017-06-14 15:04 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1497450781-52354-3-git-send-email-fschnizlein@suse.com>]
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=20170614150410.GA15806@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=fschnizlein@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=trenn@suse.com \
--cc=x86@kernel.org \
--cc=yanmin.zhang@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