mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <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>,
	"olaf@aepfle.de" <olaf@aepfle.de>,
	"apw@canonical.com" <apw@canonical.com>,
	"vkuznets@redhat.com" <vkuznets@redhat.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>
Subject: Re: [PATCH RESEND V2 0/8] Drivers: hv: vmbus: Enable unloading of vmbus driver
Date: Tue, 3 Feb 2015 16:02:58 -0800	[thread overview]
Message-ID: <20150204000258.GA24299@kroah.com> (raw)
In-Reply-To: <BY2PR0301MB0711CF108E95D94EA4857B9AA03D0@BY2PR0301MB0711.namprd03.prod.outlook.com>

On Tue, Feb 03, 2015 at 11:57:18PM +0000, KY Srinivasan wrote:
> 
> 
> > -----Original Message-----
> > From: Greg KH [mailto:gregkh@linuxfoundation.org]
> > Sent: Tuesday, February 3, 2015 3:47 PM
> > To: KY Srinivasan
> > Cc: linux-kernel@vger.kernel.org; devel@linuxdriverproject.org;
> > olaf@aepfle.de; apw@canonical.com; vkuznets@redhat.com;
> > tglx@linutronix.de
> > Subject: Re: [PATCH RESEND V2 0/8] Drivers: hv: vmbus: Enable unloading of
> > vmbus driver
> > 
> > On Wed, Jan 28, 2015 at 04:49:20PM -0800, K. Y. Srinivasan wrote:
> > > Windows hosts starting with Ws2012 R2 permit re-establishing the vmbus
> > > connection from the guest. This patch-set includes patches from Vitaly
> > > to cleanup the VMBUS unload path so we can potentially reload the driver.
> > >
> > > This set also includes a patch from Jake to correctly extract MMIO
> > > information on both Gen1 and Gen 2 firmware.
> > 
> > What changed from v1 of this series?
> > 
> > Please refresh your patch series and send _all_ patches that need to be
> > applied, I see 2 different series, and a few random patches sent out, with no
> > specific order, so I don't know what to do here :(
> >
> Ok; I will resend the entire set. Do you want me to keep the RESEND tag. 

If you use the "vX" numbering scheme, it doesn't make much sense, right?

thanks,

greg k-h

      reply	other threads:[~2015-02-04  0:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1422492560-24971-1-git-send-email-kys@microsoft.com>
2015-02-03 23:46 ` Greg KH
2015-02-03 23:57   ` KY Srinivasan
2015-02-04  0:02     ` Greg KH [this message]

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=20150204000258.GA24299@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=apw@canonical.com \
    --cc=devel@linuxdriverproject.org \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf@aepfle.de \
    --cc=tglx@linutronix.de \
    --cc=vkuznets@redhat.com \
    /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

all inboxes | Powered by JetHome®