From: Greg KH <gregkh@linuxfoundation.org>
To: Jake Oshins <jakeo@microsoft.com>
Cc: kys@microsoft.com, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, olaf@aepfle.de, apw@canonical.com,
vkuznets@redhat.com
Subject: Re: [PATCH 1/1] drivers:hv:vmbus Allow for more than one MMIO range for children.
Date: Wed, 21 Jan 2015 05:03:50 +0800 [thread overview]
Message-ID: <20150120210350.GA13258@kroah.com> (raw)
In-Reply-To: <1421791180-18810-1-git-send-email-jakeo@microsoft.com>
On Tue, Jan 20, 2015 at 01:59:40PM -0800, Jake Oshins wrote:
> Signed-off-by: Jake Oshins <jakeo@microsoft.com>
No changelog body explaining why this is needed and what it fixes?
Please redo.
next prev parent reply other threads:[~2015-01-20 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 21:59 [PATCH 1/1] drivers:hv:vmbus Allow for more than one MMIO range for children Jake Oshins
2015-01-20 21:03 ` Greg KH [this message]
2015-01-20 21:08 ` KY Srinivasan
2015-01-23 9:59 ` Vitaly Kuznetsov
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=20150120210350.GA13258@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=jakeo@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=vkuznets@redhat.com \
/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