From: Greg KH <greg@kroah.com>
To: KY Srinivasan <kys@microsoft.com>
Cc: Peter Foley <pefoley2@verizon.net>,
"gregkh@suse.de" <gregkh@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"virtualization@lists.osdl.org" <virtualization@lists.osdl.org>
Subject: Re: Hyper-V TODO file
Date: Fri, 2 Sep 2011 09:03:29 -0700 [thread overview]
Message-ID: <20110902160329.GA4682@kroah.com> (raw)
In-Reply-To: <6E21E5352C11B742B20C142EB499E048081B5FA3@TK5EX14MBXC126.redmond.corp.microsoft.com>
On Fri, Sep 02, 2011 at 03:17:19PM +0000, KY Srinivasan wrote:
>
>
> > -----Original Message-----
> > From: Greg KH [mailto:greg@kroah.com]
> > Sent: Thursday, September 01, 2011 4:31 PM
> > To: Peter Foley
> > Cc: KY Srinivasan; gregkh@suse.de; Linux Kernel Mailing List;
> > devel@linuxdriverproject.org; virtualization@lists.osdl.org
> > Subject: Re: Hyper-V TODO file
> >
> > On Wed, Aug 31, 2011 at 07:11:39PM -0400, Peter Foley wrote:
> > > On Wed, 31 Aug 2011, K. Y. Srinivasan wrote:
> > > > Greg, as I have been pestering you for some time now, we are very
> > interested in
> > > > exiting staging and we are willing to dedicate the necessary development
> > > > resources to address whatever issues that may still be pending. So, your help
> > > > in identifying what needs to be done will be greatly appreciated. To that end,
> > > > I think it will be useful to update the TODO file to reflect the current state of
> > > > the drivers. Let us know how we should proceed here.
> > >
> > > An issue I've come across in the hyper-v drivers is the forced modular
> > > build. You might want to see if the "depends on m" is still needed.
> >
> > Ah, good point, KY, can you try this out and see if that can be changed?
> > If not, something is wrong and that needs to get fixed.
>
> Just verified that we can build into the kernel (not as modules) all hyper-V
> drivers except hv_storvsc. hv_storvsc depends upon functionality that in my build
> is being built as modules (SCSI etc.) and this is the reason why I could not build
> hv_storvsc as part of the kernel.
So 'make allyesconfig' with the module dependancy turned off doesn't
break the build? If so, great.
> Greg, do you want me to submit a patch to Kconfig, getting rid of the module
> dependency (for hyperv-v drivers).
Yes please.
thanks,
greg k-h
next prev parent reply other threads:[~2011-09-02 16:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 22:16 Hyper-V TODO file K. Y. Srinivasan
2011-08-31 23:11 ` Peter Foley
2011-09-01 20:31 ` Greg KH
2011-09-02 14:09 ` KY Srinivasan
2011-09-02 15:17 ` KY Srinivasan
2011-09-02 16:03 ` Greg KH [this message]
2011-09-01 20:27 ` Greg KH
2011-09-01 20:30 ` Greg KH
2011-09-01 21:08 ` KY Srinivasan
2011-09-02 16:09 ` Greg KH
2011-09-02 19:47 ` KY Srinivasan
2011-09-02 19:58 ` Greg KH
2011-09-02 20:54 ` KY Srinivasan
2011-09-01 20:57 ` KY Srinivasan
2011-09-22 16:17 K. Y. Srinivasan
2011-09-22 16:05 ` Joe Perches
2011-09-22 17:04 ` Greg KH
2011-09-22 17:20 ` KY Srinivasan
2011-09-22 17:36 ` Greg KH
2011-09-22 18:22 ` KY Srinivasan
2011-10-04 13:59 ` KY Srinivasan
2011-10-04 17:04 ` Greg KH
2011-10-04 17:23 ` KY 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=20110902160329.GA4682@kroah.com \
--to=greg@kroah.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@suse.de \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pefoley2@verizon.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).