From: Borislav Petkov <bp@alien8.de>
To: "Tanwar, Rahul" <rahul.tanwar@linux.intel.com>
Cc: Tony Luck <tony.luck@intel.com>,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, andriy.shevchenko@intel.com,
alan@linux.intel.com, ricardo.neri-calderon@linux.intel.com,
rafael.j.wysocki@intel.com, linux-kernel@vger.kernel.org,
qi-ming.wu@intel.com, cheol.yong.kim@intel.com,
rahul.tanwar@intel.com
Subject: Re: [PATCH 2/3] x86: cpu: Add new Intel Atom CPU type
Date: Fri, 16 Aug 2019 09:38:10 +0200 [thread overview]
Message-ID: <20190816073810.GI18980@zn.tnic> (raw)
In-Reply-To: <d6452a93-16a7-451e-3abb-0bc65e89b0aa@linux.intel.com>
On Fri, Aug 16, 2019 at 03:25:51PM +0800, Tanwar, Rahul wrote:
>
> On 16/8/2019 2:43 PM, Borislav Petkov wrote:
> > Now to another question: you see how I put my reply to the previous mail
> > *below* the quoted text. Why is yours ontop? Why not put it after mine
> > since you're replying to it, like it is usually done on the mailing
> > lists and thus not confuse the reading order?
> >
> > All I'm trying to say is, please do not top-post.
>
> So sorry for missing out on this point. Will always keep in mind from now
> on.
Thanks!
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-08-16 7:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 9:46 [PATCH 0/3] x86: cpu: Add new Airmont CPU model Rahul Tanwar
2019-08-15 9:46 ` [PATCH 1/3] x86: cpu: Use constant definitions for CPU type Rahul Tanwar
2019-08-15 10:31 ` Thomas Gleixner
2019-08-16 3:17 ` Tanwar, Rahul
2019-08-15 9:46 ` [PATCH 2/3] x86: cpu: Add new Intel Atom " Rahul Tanwar
2019-08-15 12:22 ` Borislav Petkov
2019-08-16 3:22 ` Tanwar, Rahul
2019-08-16 6:43 ` Borislav Petkov
2019-08-16 7:25 ` Tanwar, Rahul
2019-08-16 7:38 ` Borislav Petkov [this message]
2019-08-15 9:46 ` [PATCH 3/3] x86: arch: Add arch support for new Intel Atom CPU Rahul Tanwar
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=20190816073810.GI18980@zn.tnic \
--to=bp@alien8.de \
--cc=alan@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=cheol.yong.kim@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=qi-ming.wu@intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rahul.tanwar@intel.com \
--cc=rahul.tanwar@linux.intel.com \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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 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.