From: Christoph Hellwig <hch@infradead.org>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, virtualization@lists.osdl.org
Subject: Re: vmbus driver
Date: Fri, 20 May 2011 08:26:49 -0400 [thread overview]
Message-ID: <20110520122649.GA550@infradead.org> (raw)
In-Reply-To: <1305842785-30206-1-git-send-email-kys@microsoft.com>
On Thu, May 19, 2011 at 03:06:25PM -0700, K. Y. Srinivasan wrote:
> A few days ago you applied all the outstanding patches for the Hyper-V
> drivers. With these patches, I have addressed all of the known review
> comments for the vmbus driver (and a lot of comments/issues in other
> drivers as well). I am still hoping I can address
> whatever other issues/comments there might be with the intention to
> get the vmbus driver out of staging in the current window. What is your
> sense in terms of how feasible this is. From my side, I can assure you
> that I will address all legitimate issues in a very timely manner and this
> will not be dependent upon the location of the drivers (staging or
> outside staging). Looking forward to hearing from you.
There's no point in merging it without a user. Make sure either
the network or storage driver is in a good enough shape to move with it,
to make sure the APIs it exports are actually sanely usable.
On the other hand the HV clocksource looks mostly mergeable and doesn't
depend on vmbus. Send a patch to add it to drivers/clocksource to the
maintainer and it should be mergeable with very little remaining
cleanup.
next prev parent reply other threads:[~2011-05-20 12:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 22:06 vmbus driver K. Y. Srinivasan
2011-05-20 12:26 ` Christoph Hellwig [this message]
2011-05-20 13:12 ` KY Srinivasan
2011-05-20 13:22 ` Christoph Hellwig
2011-05-20 14:08 ` KY Srinivasan
2011-05-20 13:36 ` KY Srinivasan
2011-05-22 10:59 ` Christoph Hellwig
2011-05-22 17:32 ` KY Srinivasan
2011-05-23 12:54 ` KY Srinivasan
2011-05-23 13:51 ` Thomas Gleixner
2011-05-23 16:16 ` KY Srinivasan
2011-05-20 13:05 ` Greg KH
2011-05-20 13:21 ` 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=20110520122649.GA550@infradead.org \
--to=hch@infradead.org \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@suse.de \
--cc=kys@microsoft.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 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).