[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFwd3zJNyy=7n945GfKYv0RhMuX6HUfDAqvZWrQyL=4GUA@mail.gmail.com>
Date:	Sat, 27 Feb 2016 10:22:04 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Bjorn Helgaas <helgaas@...nel.org>
Cc:	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Thierry Reding <treding@...dia.com>,
	Jake Oshins <jakeo@...rosoft.com>,
	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
	Олег Мороз <oleg.moroz@....vniiem.ru>,
	Sunjin Yang <fan4326@...il.com>,
	Jiang Liu <jiang.liu@...ux.intel.com>,
	"Rafael J. Wysocki" <rafael@...nel.org>
Subject: Re: [GIT PULL] PCI fixes for v4.5
On Sat, Feb 27, 2016 at 7:14 AM, Bjorn Helgaas <helgaas@...nel.org> wrote:
>
> The big chunk here is the paravirtual front-end for Linux guests of a
> Microsoft Hyper-V VM.  It's new, so no risk of regressions to pci-hyperv
> itself.  It does include minor changes to common code, but they are
> low-risk.
I really don't want to take new features like this that change
existing code when I'm about to do a rc6.
I've done late hardware-enabling pulls before with new drivers etc,
but then they are meant to enable consumer hardware that people would
have trouble getting Linux installed on etc. A paravirt Hyper-V VM
install doesn't really count as that kind of "we need to get this in
quickly out of the normal development model".
I didn't check, but can you peel off that part if it's at the top and
just send me the actual bugfixes?
                 Linus
Powered by blists - more mailing lists
 
