From: Greg KH <gregkh@suse.de>
To: Hank Janssen <hjanssen@microsoft.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Haiyang Zhang <haiyangz@microsoft.com>
Subject: Re: [PATCH 1/1] Staging: hv: Add proper versioning to HV drivers-Corrected.
Date: Thu, 11 Feb 2010 15:36:12 -0800 [thread overview]
Message-ID: <20100211233612.GB10315@suse.de> (raw)
In-Reply-To: <8AFC7968D54FB448A30D8F38F259C56212E883CB@TK5EX14MBXC118.redmond.corp.microsoft.com>
Minor nits below:
On Thu, Feb 11, 2010 at 11:02:42PM +0000, Hank Janssen wrote:
>
> Provide proper versioning information for all HV drivers.
> With removal of build time/date/and Minor number as requested
> By Greg KH
>
> Cc: Greg Kroah-Hartman <gregkh@suse.de>
> Signed-off-by: Hank Janssen <hjanssen@microsoft.com>
> Signed-off-by: Haiyang Zhang <haiyang@microsoft.com>
Don't line up the <email@domain>, just put only one space, there are a
few hundred thousand examples to look at for the correct formatting :)
>
> drivers/staging/hv/VersionInfo.h | 22 +++++++++++++++++++---
You forgot a "---" between the signed-off-by and the diffstat. If you
use either git or quilt, it will get this correct automagically. That
infers you used something else, which is quite scary. What are you
using instead to create patches?
Don't worry, I can edit this by hand when I apply it, and will do so in
a few days when I get to my "to-apply" queue, but in the future, please
don't do this.
thanks,
greg k-h
next prev parent reply other threads:[~2010-02-11 23:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 23:02 [PATCH 1/1] Staging: hv: Add proper versioning to HV drivers-Corrected Hank Janssen
2010-02-11 23:36 ` Greg KH [this message]
2010-02-12 17:55 ` Hank Janssen
2010-02-12 18:47 ` Greg KH
2010-02-12 19:39 ` Luis R. Rodriguez
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=20100211233612.GB10315@suse.de \
--to=gregkh@suse.de \
--cc=devel@driverdev.osuosl.org \
--cc=haiyangz@microsoft.com \
--cc=hjanssen@microsoft.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox