From: Christoph Hellwig <hch@infradead.org>
To: KY Srinivasan <kys@microsoft.com>
Cc: "gregkh@suse.de" <gregkh@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
"virtualization@lists.osdl.org" <virtualization@lists.osdl.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>
Subject: Re: various vmbus review comments
Date: Tue, 10 May 2011 01:24:25 -0400 [thread overview]
Message-ID: <20110510052425.GA31087@infradead.org> (raw)
In-Reply-To: <6E21E5352C11B742B20C142EB499E0481E95C6@TK5EX14MBXC128.redmond.corp.microsoft.com>
On Mon, May 09, 2011 at 02:56:52PM +0000, KY Srinivasan wrote:
> I will address this. Greg had a concern about module reference counting
> and looking at the current code, it did not appear to be an issue. The
> change you are suggesting will not affect the vmbus core which is what I want
> to focus on. I will however, fix this issue in the current round of patches I will
> send out this week.
It very clearly affects the interface between the core and the
functional drivers. Trying to submit the core without making sure the
interface is exports works properly is not an overly good idea.
next prev parent reply other threads:[~2011-05-10 5:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 20:46 various vmbus review comments Greg KH
2011-05-03 21:00 ` KY Srinivasan
2011-05-03 22:03 ` Greg KH
2011-05-03 22:49 ` KY Srinivasan
2011-05-04 16:20 ` KY Srinivasan
2011-05-04 16:32 ` Greg KH
2011-05-04 16:58 ` KY Srinivasan
2011-05-04 18:28 ` Greg KH
2011-05-06 13:10 ` KY Srinivasan
2011-05-06 14:59 ` Greg KH
2011-05-06 17:34 ` KY Srinivasan
2011-05-09 14:33 ` Christoph Hellwig
2011-05-09 14:56 ` KY Srinivasan
2011-05-10 5:24 ` Christoph Hellwig [this message]
2011-05-10 13:00 ` KY Srinivasan
2011-05-10 13:07 ` Christoph Hellwig
2011-05-10 13:16 ` Greg KH
2011-05-09 1:46 ` KY Srinivasan
2011-05-09 3:04 ` Greg KH
2011-05-09 12:35 ` 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=20110510052425.GA31087@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).