Linux virtualization list
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: KY Srinivasan <kys@microsoft.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
	"virtualization@lists.osdl.org" <virtualization@lists.osdl.org>,
	"ohering@suse.com" <ohering@suse.com>
Subject: Re: [PATCH 0000/0003] drivers: hv: util
Date: Sat, 12 May 2012 16:16:51 -0700	[thread overview]
Message-ID: <20120512231651.GB9375@kroah.com> (raw)
In-Reply-To: <426367E2313C2449837CD2DE46E7EAF90305A56E@SN2PRD0310MB382.namprd03.prod.outlook.com>

On Sat, May 12, 2012 at 08:41:06PM +0000, KY Srinivasan wrote:
> 
> 
> > -----Original Message-----
> > From: K. Y. Srinivasan [mailto:kys@microsoft.com]
> > Sent: Saturday, May 12, 2012 4:44 PM
> > To: gregkh@linuxfoundation.org; linux-kernel@vger.kernel.org;
> > devel@linuxdriverproject.org; virtualization@lists.osdl.org; ohering@suse.com
> > Cc: KY Srinivasan
> > Subject: [PATCH 0000/0003] drivers: hv: util
> 
> There are only two patches following this mail; sorry for the typo in the subject line.

What's with the 0000 stuff as well?  You do know that git send-mail can
handle all of that for you properly, right?

  reply	other threads:[~2012-05-12 23:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-12 20:44 [PATCH 0000/0003] drivers: hv: util K. Y. Srinivasan
2012-05-12 20:41 ` KY Srinivasan
2012-05-12 23:16   ` gregkh [this message]
2012-05-14 14:04     ` KY Srinivasan
2012-05-12 20:44 ` [PATCH 1/2] Drivers: hv: Get rid of an unnecessary check in vmbus_prep_negotiate_resp() K. Y. Srinivasan
2012-05-12 20:44   ` [PATCH 2/2] Drivers: hv: util: Properly handle version negotiations K. Y. Srinivasan

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=20120512231651.GB9375@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@linuxdriverproject.org \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ohering@suse.com \
    --cc=virtualization@lists.osdl.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