From: Greg KH <gregkh@suse.de>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: "devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
Haiyang Zhang <haiyangz@microsoft.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"virtualization@lists.osdl.org" <virtualization@lists.osdl.org>
Subject: Re: [PATCH 1/1] Staging: hv: Add the necessary dependencies to hyperv Kconfig
Date: Wed, 4 May 2011 11:53:38 -0700 [thread overview]
Message-ID: <20110504185338.GB9823@suse.de> (raw)
In-Reply-To: <0D753D10438DA54287A00B027084269764D295CE91@AUSP01VMBX24.collaborationhost.net>
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@microsoft.com>
> > Signed-off-by: Haiyang Zhang <haiyangz@microsoft.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.
> It also depends on IA64 || X86. Will the vmbus driver work with IA64?
No.
> If so the depends on could just be:
>
> depends on ACPI && m
No, see above for the IA64 reason.
> Also, default n is redudant since n is the default anyway.
True, but it doesn't hurt either :)
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@suse.de>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: "K. Y. Srinivasan" <kys@microsoft.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"virtualization@lists.osdl.org" <virtualization@lists.osdl.org>,
Haiyang Zhang <haiyangz@microsoft.com>
Subject: Re: [PATCH 1/1] Staging: hv: Add the necessary dependencies to hyperv Kconfig
Date: Wed, 4 May 2011 11:53:38 -0700 [thread overview]
Message-ID: <20110504185338.GB9823@suse.de> (raw)
In-Reply-To: <0D753D10438DA54287A00B027084269764D295CE91@AUSP01VMBX24.collaborationhost.net>
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@microsoft.com>
> > Signed-off-by: Haiyang Zhang <haiyangz@microsoft.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.
> It also depends on IA64 || X86. Will the vmbus driver work with IA64?
No.
> If so the depends on could just be:
>
> depends on ACPI && m
No, see above for the IA64 reason.
> Also, default n is redudant since n is the default anyway.
True, but it doesn't hurt either :)
thanks,
greg k-h
next prev parent reply other threads:[~2011-05-04 18:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 18:51 [PATCH 1/1] Staging: hv: Add the necessary dependencies to hyperv Kconfig K. Y. Srinivasan
2011-05-04 18:44 ` H Hartley Sweeten
2011-05-04 18:44 ` H Hartley Sweeten
2011-05-04 18:48 ` KY Srinivasan
2011-05-04 18:48 ` KY Srinivasan
2011-05-04 18:53 ` Greg KH [this message]
2011-05-04 18:53 ` Greg KH
2011-05-04 19:33 ` Randy Dunlap
2011-05-04 19:33 ` Randy Dunlap
2011-05-04 19:39 ` Greg KH
2011-05-04 19:54 ` KY Srinivasan
2011-05-04 19:58 ` Greg KH
2011-05-04 19:55 ` Randy Dunlap
2011-05-04 18:51 ` Christoph Hellwig
2011-05-04 18:59 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2011-05-04 19:19 K. Y. Srinivasan
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=20110504185338.GB9823@suse.de \
--to=gregkh@suse.de \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=hartleys@visionengravers.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.