lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150204000258.GA24299@kroah.com>
Date:	Tue, 3 Feb 2015 16:02:58 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	KY Srinivasan <kys@...rosoft.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
	"olaf@...fle.de" <olaf@...fle.de>,
	"apw@...onical.com" <apw@...onical.com>,
	"vkuznets@...hat.com" <vkuznets@...hat.com>,
	"tglx@...utronix.de" <tglx@...utronix.de>
Subject: Re: [PATCH RESEND V2 0/8] Drivers: hv: vmbus: Enable unloading of
 vmbus driver

On Tue, Feb 03, 2015 at 11:57:18PM +0000, KY Srinivasan wrote:
> 
> 
> > -----Original Message-----
> > From: Greg KH [mailto:gregkh@...uxfoundation.org]
> > Sent: Tuesday, February 3, 2015 3:47 PM
> > To: KY Srinivasan
> > Cc: linux-kernel@...r.kernel.org; devel@...uxdriverproject.org;
> > olaf@...fle.de; apw@...onical.com; vkuznets@...hat.com;
> > tglx@...utronix.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ