From: "Jan Beulich" <JBeulich@suse.com>
To: "KY Srinivasan" <kys@microsoft.com>, "H. Peter Anvin" <hpa@zytor.com>
Cc: "olaf@aepfle.de" <olaf@aepfle.de>, "bp@alien8.de" <bp@alien8.de>,
"apw@canonical.com" <apw@canonical.com>,
"x86@kernel.org" <x86@kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH V2 1/1] X86: Hyper-V: Get the local APIC timer frequency from the hypervisor
Date: Fri, 13 Sep 2013 07:39:08 +0100 [thread overview]
Message-ID: <5232CF2C02000078000F2ED9@nat28.tlf.novell.com> (raw)
In-Reply-To: <50f92d9c16a54e5bb6fa14ef72e5fdfb@SN2PR03MB061.namprd03.prod.outlook.com>
>>> On 13.09.13 at 03:43, KY Srinivasan <kys@microsoft.com> wrote:
>
>> -----Original Message-----
>> From: H. Peter Anvin [mailto:hpa@zytor.com]
>> Sent: Thursday, September 12, 2013 5:28 PM
>> To: KY Srinivasan
>> Cc: x86@kernel.org; gregkh@linuxfoundation.org; linux-kernel@vger.kernel.org;
>> devel@linuxdriverproject.org; olaf@aepfle.de; apw@canonical.com;
>> jasowang@redhat.com; tglx@linutronix.de; JBeulich@suse.com; bp@alien8.de
>> Subject: Re: [PATCH V2 1/1] X86: Hyper-V: Get the local APIC timer frequency
>> from the hypervisor
>>
>> On 09/12/2013 05:06 PM, KY Srinivasan wrote:
>> >
>> > Peter,
>> >
>> > Let me know if you want me to address any additional issues in this patch.
>> >
>>
>> Please address Jan and Gleb's feedback.
>
> Gleb's feedback was a question and I answered that as I did Jan's feedback
> as well.
> Gleb, Jan, please let me know if there is something else you want addressed
> here.
Indeed, apart from the question whether to change that one
message's level from KERN_INFO to KERN_DEBUG, there was
nothing really left unexplained (the aspect of the artificial tying
together of distinct features is really something KY has to
decide - I merely tried to point out that this is odd).
Jan
next prev parent reply other threads:[~2013-09-13 6:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 18:30 K. Y. Srinivasan
2013-09-04 7:17 ` Jan Beulich
2013-09-04 15:03 ` KY Srinivasan
2013-09-04 9:40 ` Gleb Natapov
2013-09-04 15:16 ` KY Srinivasan
2013-09-05 14:16 ` Gleb Natapov
2013-09-13 0:06 ` KY Srinivasan
2013-09-13 0:28 ` H. Peter Anvin
2013-09-13 1:43 ` KY Srinivasan
2013-09-13 6:39 ` Jan Beulich [this message]
2013-09-13 14:28 ` KY Srinivasan
2013-09-13 9:55 ` Gleb Natapov
2013-09-13 14:28 ` KY Srinivasan
2013-09-17 13:59 ` Gleb Natapov
2013-09-17 19:53 ` KY Srinivasan
2013-09-18 5:43 ` Gleb Natapov
2013-09-23 13:02 ` KY Srinivasan
2013-09-23 15:50 ` H. Peter Anvin
2013-09-23 19:23 ` KY Srinivasan
2013-10-02 23:11 ` KY Srinivasan
2013-09-27 15:10 ` Olaf Hering
2013-09-27 15:23 ` KY Srinivasan
2013-09-27 15:32 ` Olaf Hering
2013-09-27 15:35 ` KY Srinivasan
2013-10-09 22:50 ` H. Peter Anvin
2013-10-10 0:04 ` 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=5232CF2C02000078000F2ED9@nat28.tlf.novell.com \
--to=jbeulich@suse.com \
--cc=apw@canonical.com \
--cc=bp@alien8.de \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®