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
| ||
|
Date: Wed, 4 May 2011 12:39:54 -0700 From: Greg KH <gregkh@...e.de> To: Randy Dunlap <rdunlap@...otime.net> Cc: H Hartley Sweeten <hartleys@...ionengravers.com>, "devel@...uxdriverproject.org" <devel@...uxdriverproject.org>, Haiyang Zhang <haiyangz@...rosoft.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "virtualization@...ts.osdl.org" <virtualization@...ts.osdl.org> Subject: Re: [PATCH 1/1] Staging: hv: Add the necessary dependencies to hyperv Kconfig On Wed, May 04, 2011 at 12:33:02PM -0700, Randy Dunlap wrote: > On Wed, 4 May 2011 11:53:38 -0700 Greg KH wrote: > > > On Wed, May 04, 2011 at 01:44:27PM -0500, H Hartley Sweeten wrote: > > > On Wednesday, May 04, 2011 11:52 AM, K. Y. Srinivasan wrote: > > > > > > > > The vmbus driver dependes on ACPI and PCI subsystems. Change > > > > Kconfig to reflect this. > > > > > > > > Signed-off-by: K. Y. Srinivasan <kys@...rosoft.com> > > > > Signed-off-by: Haiyang Zhang <haiyangz@...rosoft.com> > > > > --- > > > > drivers/staging/hv/Kconfig | 2 +- > > > > 1 files changed, 1 insertions(+), 1 deletions(-) > > > > > > > > diff --git a/drivers/staging/hv/Kconfig b/drivers/staging/hv/Kconfig > > > > index 76f0756..5e0c9f6 100644 > > > > --- a/drivers/staging/hv/Kconfig > > > > +++ b/drivers/staging/hv/Kconfig > > > > @@ -1,6 +1,6 @@ > > > > config HYPERV > > > > tristate "Microsoft Hyper-V client drivers" > > > > - depends on X86 && m > > > > + depends on X86 && ACPI && PCI && m > > > > default n > > > > help > > > > Select this option to run Linux as a Hyper-V client operating > > > > > > ACPI itself depends on PCI. > > > > Still? I thought that got removed a while ago. > > Still. Len has written in the past that technically there is no such > dependency, but in reality there is, for now at least. IIRC. Ok, but then we should still say we depend on PCI to handle if/when ACPI removes that dependancy in the future. It doesn't hurt here at all. 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