public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudeep Dutt <sudeep.dutt@intel.com>
Cc: Joe Perches <joe@perches.com>,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	Nikhil Rao <nikhil.rao@intel.com>,
	Ashutosh Dixit <ashutosh.dixit@intel.com>,
	Dasaratharaman Chandramouli 
	<dasaratharaman.chandramouli@intel.com>,
	Harshavardhan R Kharche <harshavardhan.r.kharche@intel.com>,
	"Yaozu (Eddie) Dong" <eddie.dong@intel.com>,
	Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>
Subject: Re: [PATCH CHAR-MISC-NEXT 1/4] Intel MIC Host Driver Sysfs Cleanups.
Date: Thu, 26 Sep 2013 20:15:21 -0700	[thread overview]
Message-ID: <20130927031521.GA13086@kroah.com> (raw)
In-Reply-To: <14836f009d68ee2fb29501cc711f31176486e2f0.1380241770.git.sudeep.dutt@intel.com>

On Thu, Sep 26, 2013 at 06:09:51PM -0700, Sudeep Dutt wrote:
> + Use DEVICE_ATTR_RO/RW instead of DEVICE_ATTR
> + Use ATTRIBUTE_GROUPS
> 
> These changes were suggested by Greg Kroah-Hartman during the
> code review @ https://lkml.org/lkml/2013/9/6/13
> 
> Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> Signed-off-by: Dasaratharaman Chandramouli <dasaratharaman.chandramouli@intel.com>
> Signed-off-by: Nikhil Rao <nikhil.rao@intel.com>
> Signed-off-by: Harshavardhan R Kharche <harshavardhan.r.kharche@intel.com>
> Signed-off-by: Sudeep Dutt <sudeep.dutt@intel.com>
> ---

Ok, new kernel developer 101 training time :)

Your Subject:, while the [PATCH] part is fine the rest of the line needs
to be a bit more descriptive.

As this is the "mic" subsystem, how about something like:
	Subject: [PATCH 1/4] misc: mic: host driver sysfs cleanups

No need for the whole "Intel MIC" stuff.

Also, as I "reported" this, you should have a:
	Reported-by: Greg Kroah-Hartman <...>
line in the patch.

And really, all of those people reviewed and signed off on the patch?
That's great, just not a normal thing.

So, can you resend these 4 patches with those things cleaned up?  Same
thing goes for Joe's patch, he deserves a "Reported-by:" at the very
least, given that he pretty much wrote that whole patch.

thanks,

greg k-h

  reply	other threads:[~2013-09-27  3:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-27  1:09 [PATCH CHAR-MISC-NEXT 0/4] Intel MIC Driver Cleanups Sudeep Dutt
2013-09-27  1:09 ` [PATCH CHAR-MISC-NEXT 1/4] Intel MIC Host Driver Sysfs Cleanups Sudeep Dutt
2013-09-27  3:15   ` Greg Kroah-Hartman [this message]
2013-09-27  1:10 ` [PATCH CHAR-MISC-NEXT 2/4] Intel MIC Driver Header File Cleanups Sudeep Dutt
2013-09-27  3:16   ` Greg Kroah-Hartman
2013-09-27  1:10 ` [PATCH CHAR-MISC-NEXT 3/4] Intel MIC Driver Cleanups for "--strict" checkpatch Sudeep Dutt
2013-09-27  1:10 ` [PATCH CHAR-MISC-NEXT 4/4] Intel MIC Header File warning fix Sudeep Dutt
2013-09-27  3:17   ` Greg Kroah-Hartman
2013-09-27 19:37     ` Sudeep Dutt

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=20130927031521.GA13086@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ashutosh.dixit@intel.com \
    --cc=dasaratharaman.chandramouli@intel.com \
    --cc=eddie.dong@intel.com \
    --cc=harshavardhan.r.kharche@intel.com \
    --cc=joe@perches.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nikhil.rao@intel.com \
    --cc=peter.p.waskiewicz.jr@intel.com \
    --cc=sudeep.dutt@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