From: Greg KH <gregkh@suse.de>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: devel@linuxdriverproject.org,
Haiyang Zhang <haiyangz@microsoft.com>,
linux-kernel@vger.kernel.org, virtualization@lists.osdl.org
Subject: Re: [PATCH 1/1] Staging: hv: Integrate the time source driver with Hyper-V detection code
Date: Wed, 29 Jun 2011 12:06:42 -0700 [thread overview]
Message-ID: <20110629190642.GA19698@suse.de> (raw)
In-Reply-To: <1309374364-23528-1-git-send-email-kys@microsoft.com>
On Wed, Jun 29, 2011 at 12:06:04PM -0700, K. Y. Srinivasan wrote:
> The Hyper-V timesource driver is best integrated with Hyper-V detection code
> since: (a) Linux guests running on Hyper-V need this timesource and (b)
> by integrating with Hyper-V detection, we could minimize the code in the
> timesource driver. Greg, you had helped me initially in getting the Hyper-V
> detection code into the kernel (mshyperv.c). I am hoping you can take
> this patch.
Nope, it needs to go through the x86 maintainers, please resend it to
them. The scripts/get_maintainer.pl file should have told you this,
right?
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@suse.de>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
virtualization@lists.osdl.org,
Haiyang Zhang <haiyangz@microsoft.com>
Subject: Re: [PATCH 1/1] Staging: hv: Integrate the time source driver with Hyper-V detection code
Date: Wed, 29 Jun 2011 12:06:42 -0700 [thread overview]
Message-ID: <20110629190642.GA19698@suse.de> (raw)
In-Reply-To: <1309374364-23528-1-git-send-email-kys@microsoft.com>
On Wed, Jun 29, 2011 at 12:06:04PM -0700, K. Y. Srinivasan wrote:
> The Hyper-V timesource driver is best integrated with Hyper-V detection code
> since: (a) Linux guests running on Hyper-V need this timesource and (b)
> by integrating with Hyper-V detection, we could minimize the code in the
> timesource driver. Greg, you had helped me initially in getting the Hyper-V
> detection code into the kernel (mshyperv.c). I am hoping you can take
> this patch.
Nope, it needs to go through the x86 maintainers, please resend it to
them. The scripts/get_maintainer.pl file should have told you this,
right?
thanks,
greg k-h
next prev parent reply other threads:[~2011-06-29 19:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 19:06 [PATCH 1/1] Staging: hv: Integrate the time source driver with Hyper-V detection code K. Y. Srinivasan
2011-06-29 19:06 ` Greg KH [this message]
2011-06-29 19:06 ` Greg KH
2011-06-30 0:42 ` KY Srinivasan
-- strict thread matches above, loose matches on Subject: below --
2011-06-30 0:58 K. Y. Srinivasan
2011-07-16 1:01 K. Y. Srinivasan
2011-07-18 14:53 ` KY Srinivasan
2011-07-18 14:53 ` KY Srinivasan
2011-08-02 16:03 K. Y. Srinivasan
2011-09-02 8:13 ` Thomas Gleixner
2011-09-02 13:30 ` KY Srinivasan
2011-09-02 13:30 ` KY Srinivasan
2011-09-07 22:25 K. Y. Srinivasan
2011-09-09 20:32 ` Greg KH
2011-09-09 20:32 ` 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=20110629190642.GA19698@suse.de \
--to=gregkh@suse.de \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.