From: Greg KH <gregkh@suse.de>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "K. Y. Srinivasan" <kys@microsoft.com>,
James.Bottomley@hansenpartnership.com, hch@infradead.org,
linux-scsi@vger.kernel.org
Subject: Re: hv_storvsc driver
Date: Thu, 17 Nov 2011 09:41:32 -0800 [thread overview]
Message-ID: <20111117174132.GA13208@suse.de> (raw)
In-Reply-To: <CAO+b5-pn1GswdXXB=EVThaoWaSW2EJmB=_GAE93Fa9+EeYxR1g@mail.gmail.com>
On Thu, Nov 17, 2011 at 06:27:00PM +0100, Bart Van Assche wrote:
> On Thu, Nov 17, 2011 at 6:10 PM, K. Y. Srinivasan <kys@microsoft.com> wrote:
> > Sometime back I had sent the scsi mailing list, the patch to move the
> > Hyper-V storage driver out of staging. This patch addresses most of the
> > review comments I have gotten to date from you and Christoph (I have not heard
> > from anybody else in scsi mailing list). The patches addressing the review comments
> > have already been sent to the staging tree. Let me know what I can do to expedite the
> > move from the staging tree.
>
> I've noticed that commit 46a971913611a23478283931460a95be962ce329
> added an entry for the Hyper-V drivers directly under "Device
> Drivers", that there exists an entry "Device Drivers/Virtio drivers",
> that there exists an entry "Device Drivers/SCSI device support/SCSI
> low-level drivers/VMware PVSCSI driver support" and also that there
> exists an entry "Processor type and features/Paravirtualized guest
> support/Xen guest support" . IMHO we should be able to come up with a
> less confusing config menu structure for paravirtualized guest
> support.
Patches are always gladly welcomed.
thanks,
greg k-h
next prev parent reply other threads:[~2011-11-17 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 17:10 hv_storvsc driver K. Y. Srinivasan
2011-11-17 17:27 ` Bart Van Assche
2011-11-17 17:41 ` Greg KH [this message]
2011-11-18 0:43 ` KY Srinivasan
-- strict thread matches above, loose matches on Subject: below --
2011-12-13 15:58 K. Y. Srinivasan
2011-12-13 16:07 ` Greg KH
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=20111117174132.GA13208@suse.de \
--to=gregkh@suse.de \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bvanassche@acm.org \
--cc=hch@infradead.org \
--cc=kys@microsoft.com \
--cc=linux-scsi@vger.kernel.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