From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Stephen Hemminger <sthemmin@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH 1/2] hyperv: implement hv_get_tsc_page()
Date: Thu, 9 Feb 2017 15:17:29 -0800 [thread overview]
Message-ID: <20170209151729.6c88b779@xeon-e3> (raw)
In-Reply-To: <alpine.DEB.2.20.1702092112340.4500@nanos>
On Thu, 9 Feb 2017 21:14:25 +0100 (CET)
Thomas Gleixner <tglx@linutronix.de> wrote:
> On Thu, 9 Feb 2017, Stephen Hemminger wrote:
>
> > The actual code looks fine, but the style police will not like you.
> > { should be at start of line on functions.
> > And #else should be at start of line,
> >
> > But maybe this was just more of exchange mangling the mail.
>
> Looks like.
>
> > +struct ms_hyperv_tsc_page *hv_get_tsc_page(void) {
> > + return tsc_pg;
> > +}
> > +
>
> That's how it reads in a proper mail client connected to a proper mail
> server:
>
> > +struct ms_hyperv_tsc_page *hv_get_tsc_page(void)
> > +{
> > + return tsc_pg;
> > +}
>
> :)
Yup. it looks like the mail server is trying to be "helpful" by eliminating extra white space.
next prev parent reply other threads:[~2017-02-09 23:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 14:10 [PATCH 0/2] x86/vdso: Add Hyper-V TSC page clocksource support Vitaly Kuznetsov
2017-02-09 14:10 ` [PATCH 1/2] hyperv: implement hv_get_tsc_page() Vitaly Kuznetsov
2017-02-09 18:24 ` Stephen Hemminger
2017-02-09 20:14 ` Thomas Gleixner
2017-02-09 23:17 ` Stephen Hemminger [this message]
2017-02-09 14:10 ` [PATCH 2/2] x86/vdso: Add VCLOCK_HVCLOCK vDSO clock read method Vitaly Kuznetsov
2017-02-09 17:08 ` Thomas Gleixner
2017-02-09 18:27 ` Stephen Hemminger
2017-02-10 12:25 ` Vitaly Kuznetsov
2017-02-10 12:28 ` Thomas Gleixner
2017-02-10 16:31 ` Stephen Hemminger
2017-02-10 18:01 ` Thomas Gleixner
2017-02-13 7:49 ` Dexuan Cui
2017-02-13 9:27 ` Thomas Gleixner
2017-02-13 19:06 ` Andy Lutomirski
2017-02-13 19:28 ` Thomas Gleixner
2017-02-09 20:45 ` KY Srinivasan
2017-02-09 22:55 ` Andy Lutomirski
2017-02-09 23:15 ` Stephen Hemminger
2017-02-10 12:15 ` Vitaly Kuznetsov
2017-02-10 11:06 ` Vitaly Kuznetsov
2017-02-10 11:15 ` Thomas Gleixner
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=20170209151729.6c88b779@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=sthemmin@microsoft.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--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