All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
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>
Subject: Re: [PATCH 00/12] Staging: hv: Cleanup vmbus driver - Phase II
Date: Tue, 15 Mar 2011 15:30:32 -0700	[thread overview]
Message-ID: <20110315223032.GA9046@suse.de> (raw)
In-Reply-To: <6E21E5352C11B742B20C142EB499E048019A87@TK5EX14MBXC128.redmond.corp.microsoft.com>

On Tue, Mar 15, 2011 at 10:24:41PM +0000, KY Srinivasan wrote:
> 
> 
> > -----Original Message-----
> > From: Greg KH [mailto:gregkh@suse.de]
> > Sent: Tuesday, March 15, 2011 6:05 PM
> > To: KY Srinivasan
> > Cc: linux-kernel@vger.kernel.org; devel@linuxdriverproject.org;
> > virtualization@lists.osdl.org
> > Subject: Re: [PATCH 00/12] Staging: hv: Cleanup vmbus driver - Phase II
> > 
> > On Tue, Mar 15, 2011 at 03:02:07PM -0700, K. Y. Srinivasan wrote:
> > > This patch-set fixes the following issues in the vmbus driver (vmbus_drv.c):
> > 
> > <snip>
> > 
> > Thanks for the patches, but as the .39 merge window is closed, I'll be
> > holding on to these until after .39-rc1 is out before I can do anything
> > with them.
> > 
> > So don't be surprised if I don't respond to them for a few weeks.  Don't
> > worry, they aren't lost. :)
> 
> If possible, I would love to get your feedback even if you cannot check 
> in these patches. Also, if you can give me feedback as to what else
> would need to be fixed to exit staging  as far as the vmbus driver is 
> concerned, I can work on those over the next couple of weeks
> until the tree opens up.

As I'm going to be very busy with the merge window issues, coupled with
spring break and the LF Collab summit, I doubt I'll be able to do this,
sorry.  Give me a few weeks please.

> If it is ok with you we will send the DPRINT cleanup patches in the
> next couple of days.

That's fine, they can sit in the same "to-apply" mbox next to these :)

greg k-h

  reply	other threads:[~2011-03-15 22:30 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15 22:02 [PATCH 00/12] Staging: hv: Cleanup vmbus driver - Phase II K. Y. Srinivasan
2011-03-15 22:03 ` [PATCH 01/12] Staging: hv: Make vmbus driver a pci driver K. Y. Srinivasan
2011-03-15 22:03   ` K. Y. Srinivasan
2011-03-15 22:03   ` [PATCH 02/12] Staging: hv: Cleanup root device handling K. Y. Srinivasan
2011-03-15 22:03     ` K. Y. Srinivasan
2011-03-15 22:03     ` [PATCH 03/12] Staging: hv: Cleanup irq management K. Y. Srinivasan
2011-03-15 22:03       ` [PATCH 04/12] Staging: hv: Rename vmbus_driver_context structure K. Y. Srinivasan
2011-03-15 22:03         ` K. Y. Srinivasan
2011-03-15 22:03         ` [PATCH 05/12] Get rid of the forward declaration for vmbus_uevent K. Y. Srinivasan
2011-03-15 22:03           ` K. Y. Srinivasan
2011-03-15 22:03           ` [PATCH 05/12] Staging: hv: " K. Y. Srinivasan
2011-03-15 22:03             ` [PATCH 06/12] Staging: hv: Get rid of the forward declaration for vmbus_match K. Y. Srinivasan
2011-03-15 22:03               ` K. Y. Srinivasan
2011-03-15 22:03               ` [PATCH 07/12] Staging: hv: Get rid of the forward declaration for vmbus_probe K. Y. Srinivasan
2011-03-15 22:03                 ` K. Y. Srinivasan
2011-03-15 22:03                 ` [PATCH 08/12] Staging: hv: Get rid of the forward declaration for vmbus_remove K. Y. Srinivasan
2011-03-15 22:03                   ` K. Y. Srinivasan
2011-03-15 22:03                   ` [PATCH 09/12] Staging: hv: Get rid of the forward declaration for vmbus_shutdown K. Y. Srinivasan
2011-03-15 22:03                     ` K. Y. Srinivasan
2011-03-15 22:03                     ` [PATCH 10/12] Staging: hv: Get rid of the forward declaration for vmbus_device_release K. Y. Srinivasan
2011-03-15 22:03                       ` K. Y. Srinivasan
2011-03-15 22:03                       ` [PATCH 11/12] Staging: hv: Get rid of the forward declaration for vmbus_isr K. Y. Srinivasan
2011-03-15 22:03                         ` K. Y. Srinivasan
2011-03-15 22:03                         ` [PATCH 12/12] Staging: hv: Get rid of the forward declaration for vmbus_show_device_attr K. Y. Srinivasan
2011-03-15 22:03                           ` K. Y. Srinivasan
2011-03-15 22:22             ` [PATCH 05/12] Staging: hv: Get rid of the forward declaration for vmbus_uevent Greg KH
2011-03-15 22:23               ` Greg KH
2011-03-15 22:39               ` KY Srinivasan
2011-03-15 22:51                 ` Greg KH
2011-04-05  4:22         ` [PATCH 04/12] Staging: hv: Rename vmbus_driver_context structure Greg KH
2011-04-05  4:19       ` [PATCH 03/12] Staging: hv: Cleanup irq management Greg KH
2011-04-05  4:16   ` [PATCH 01/12] Staging: hv: Make vmbus driver a pci driver Greg KH
2011-04-05  4:16     ` Greg KH
2011-03-15 22:04 ` [PATCH 00/12] Staging: hv: Cleanup vmbus driver - Phase II Greg KH
2011-03-15 22:24   ` KY Srinivasan
2011-03-15 22:30     ` Greg KH [this message]
2011-03-17 21:39   ` Valdis.Kletnieks
2011-03-17 21:45     ` Greg KH
2011-03-17 22:58       ` Valdis.Kletnieks
2011-04-16  0:34     ` Greg KH
2011-04-16  0:34       ` Greg KH

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=20110315223032.GA9046@suse.de \
    --to=gregkh@suse.de \
    --cc=devel@linuxdriverproject.org \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.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.