From: Greg KH <greg@kroah.com>
To: KY Srinivasan <kys@microsoft.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
"r@home.goodmis.org" <r@home.goodmis.org>,
"gregkh@suse.de" <gregkh@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"virtualization@lists.osdl.org" <virtualization@lists.osdl.org>,
Haiyang Zhang <haiyangz@microsoft.com>,
Hank Janssen <hjanssen@microsoft.com>
Subject: Re: [PATCH 1/6] Staging: hv: Unify hyper-v device abstractions
Date: Mon, 28 Feb 2011 18:28:39 -0800 [thread overview]
Message-ID: <20110301022839.GA1663@kroah.com> (raw)
In-Reply-To: <6E21E5352C11B742B20C142EB499E048015786@TK5EX14MBXC128.redmond.corp.microsoft.com>
On Sat, Feb 26, 2011 at 05:13:34PM +0000, KY Srinivasan wrote:
>
>
> > -----Original Message-----
> > From: Steven Rostedt [mailto:rostedt@goodmis.org]
> > Sent: Friday, February 25, 2011 10:21 PM
> > To: KY Srinivasan; r@home.goodmis.org
> > Cc: gregkh@suse.de; linux-kernel@vger.kernel.org;
> > devel@linuxdriverproject.org; virtualization@lists.osdl.org; Haiyang Zhang; Hank
> > Janssen
> > Subject: Re: [PATCH 1/6] Staging: hv: Unify hyper-v device abstractions
> >
> > Hi!
> >
> > Just an FYI,
> >
> > When sending out patch series, could you send out a [PATCH 0/6] first,
> > and have all other patches a reply to that patch. Both git and quilt
> > have ways to do this.
>
> My mistake; I numbered the patches 1 through 6 as opposed to 0 through 5.
> Sorry for the confusion.
Wait, what?
So, what should I apply here, only patches 2-6? What is patch 1 for
then?
still totally confused,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: KY Srinivasan <kys@microsoft.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
"r@home.goodmis.org" <r@rostedt.homelinux.com>,
"gregkh@suse.de" <gregkh@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"virtualization@lists.osdl.org" <virtualization@lists.osdl.org>,
Haiyang Zhang <haiyangz@microsoft.com>,
Hank Janssen <hjanssen@microsoft.com>
Subject: Re: [PATCH 1/6] Staging: hv: Unify hyper-v device abstractions
Date: Mon, 28 Feb 2011 18:28:39 -0800 [thread overview]
Message-ID: <20110301022839.GA1663@kroah.com> (raw)
In-Reply-To: <6E21E5352C11B742B20C142EB499E048015786@TK5EX14MBXC128.redmond.corp.microsoft.com>
On Sat, Feb 26, 2011 at 05:13:34PM +0000, KY Srinivasan wrote:
>
>
> > -----Original Message-----
> > From: Steven Rostedt [mailto:rostedt@goodmis.org]
> > Sent: Friday, February 25, 2011 10:21 PM
> > To: KY Srinivasan; r@home.goodmis.org
> > Cc: gregkh@suse.de; linux-kernel@vger.kernel.org;
> > devel@linuxdriverproject.org; virtualization@lists.osdl.org; Haiyang Zhang; Hank
> > Janssen
> > Subject: Re: [PATCH 1/6] Staging: hv: Unify hyper-v device abstractions
> >
> > Hi!
> >
> > Just an FYI,
> >
> > When sending out patch series, could you send out a [PATCH 0/6] first,
> > and have all other patches a reply to that patch. Both git and quilt
> > have ways to do this.
>
> My mistake; I numbered the patches 1 through 6 as opposed to 0 through 5.
> Sorry for the confusion.
Wait, what?
So, what should I apply here, only patches 2-6? What is patch 1 for
then?
still totally confused,
greg k-h
next prev parent reply other threads:[~2011-03-01 2:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-26 2:05 [PATCH 1/6] Staging: hv: Unify hyper-v device abstractions K. Y. Srinivasan
2011-02-26 3:21 ` Steven Rostedt
2011-02-26 3:21 ` Steven Rostedt
2011-02-26 17:13 ` KY Srinivasan
2011-02-26 17:13 ` KY Srinivasan
2011-02-26 17:13 ` KY Srinivasan
2011-02-26 17:13 ` KY Srinivasan
2011-03-01 2:28 ` Greg KH [this message]
2011-03-01 2:28 ` Greg KH
2011-03-01 2:34 ` Greg KH
2011-03-02 1:40 ` KY Srinivasan
2011-03-02 6:35 ` Dan Carpenter
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=20110301022839.GA1663@kroah.com \
--to=greg@kroah.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@suse.de \
--cc=haiyangz@microsoft.com \
--cc=hjanssen@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=r@home.goodmis.org \
--cc=rostedt@goodmis.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.