From: Greg KH <greg@kroah.com>
To: Haiyang Zhang <haiyangz@microsoft.com>
Cc: "gregkh@suse.de" <gregkh@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
NetDev <netdev@vger.kernel.org>
Subject: Re: [PATCH] staging: hv: move hv_netvsc out of staging area
Date: Wed, 30 Nov 2011 00:16:38 +0900 [thread overview]
Message-ID: <20111129151638.GB24688@kroah.com> (raw)
In-Reply-To: <A1F3067C9B68744AA19F6802BAB8FFDC0CCCC087@TK5EX14MBXC227.redmond.corp.microsoft.com>
On Mon, Nov 28, 2011 at 10:00:35PM +0000, Haiyang Zhang wrote:
> > -----Original Message-----
> > From: Haiyang Zhang [mailto:haiyangz@microsoft.com]
> > Sent: Monday, November 28, 2011 4:36 PM
> > To: Haiyang Zhang; KY Srinivasan; gregkh@suse.de; linux-
> > kernel@vger.kernel.org; devel@linuxdriverproject.org
> > Cc: Mike Sterling; NetDev
> > Subject: [PATCH] staging: hv: move hv_netvsc out of staging area
> >
> > hv_netvsc has been reviewed on netdev mailing list on 6/09/2011.
> > All recommended changes have been made. We are requesting to move it
> > out of staging area.
> >
> > Signed-off-by: Haiyang Zhang <haiyangz@microsoft.com>
> > Signed-off-by: KY Srinivasan <kys@microsoft.com>
> > Signed-off-by: Mike Sterling <Mike.Sterling@microsoft.com>
> > Cc: NetDev <netdev@vger.kernel.org>
> > Acked-by: Stephen Hemminger <shemminger@vyatta.com>
> > ---
> > drivers/net/Kconfig | 2 ++
> > drivers/net/Makefile | 2 ++
> > drivers/net/hyperv/Kconfig | 5 +++++
> > drivers/net/hyperv/Makefile | 3 +++
> > drivers/{staging/hv => net/hyperv}/hyperv_net.h | 0
> > drivers/{staging/hv => net/hyperv}/netvsc.c | 0
> > drivers/{staging/hv => net/hyperv}/netvsc_drv.c | 0
> > drivers/{staging/hv => net/hyperv}/rndis_filter.c | 0
> > drivers/staging/hv/Kconfig | 6 ------
> > drivers/staging/hv/Makefile | 2 --
> > drivers/staging/hv/TODO | 1 -
> > 11 files changed, 12 insertions(+), 9 deletions(-) create mode 100644
> > drivers/net/hyperv/Kconfig create mode 100644
> > drivers/net/hyperv/Makefile rename drivers/{staging/hv =>
> > net/hyperv}/hyperv_net.h (100%) rename drivers/{staging/hv =>
> > net/hyperv}/netvsc.c (100%) rename drivers/{staging/hv =>
> > net/hyperv}/netvsc_drv.c (100%) rename drivers/{staging/hv =>
> > net/hyperv}/rndis_filter.c (100%)
> >
>
> I have rebased the previous patch on the latest staging-next branch,
> and re-submitting it now. In another email, the same patch was
> submitted without using the "-M" flag, in case anyone wants to read
> the unchanged code in the patch body.
This one was fine, now applied, thanks.
greg k-h
next prev parent reply other threads:[~2011-11-29 15:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 21:35 [PATCH] staging: hv: move hv_netvsc out of staging area Haiyang Zhang
2011-11-28 22:00 ` Haiyang Zhang
2011-11-29 15:16 ` Greg KH [this message]
2011-11-29 18:05 ` Haiyang Zhang
-- strict thread matches above, loose matches on Subject: below --
2011-10-14 19:20 Haiyang Zhang
2011-10-14 19:12 ` Stephen Hemminger
2011-10-14 19:16 ` Greg KH
2011-10-14 19:28 ` Haiyang Zhang
2011-10-14 19:35 ` Sasha Levin
2011-10-14 19:40 ` Haiyang Zhang
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=20111129151638.GB24688@kroah.com \
--to=greg@kroah.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@suse.de \
--cc=haiyangz@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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