From: Len Brown <lenb@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
X86 ML <x86@kernel.org>, Linux PM list <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Len Brown <len.brown@intel.com>
Subject: Re: [PATCH 1/1] x86: replace cpu_up hard-coded mdelay with variable
Date: Fri, 1 May 2015 14:02:41 -0700 [thread overview]
Message-ID: <CAJvTdKnv8ibbu3NyQ4j62HbR7Sc92xF-DUQfsMuxGFf3-4Geiw@mail.gmail.com> (raw)
In-Reply-To: <20150422060734.GA25230@gmail.com>
On Tue, Apr 21, 2015 at 11:07 PM, Ingo Molnar <mingo@kernel.org> wrote:
>
> * Paul Gortmaker <paul.gortmaker@windriver.com> wrote:
>> Happened to notice a 2x "The the..." when I came across this in
>> linux-next today and was reading the help out of curiousity...
>
> Len, this commit isn't in a permanent Git tree yet, right? We want to
> do this through the x86 tree, and along the suggestions I made.
It was in my -next tree -- no not permanent, yes, since removed (today).
Yes, I plan to send you a v2 and TIP is the right place for it to live.
Paul, thanks for noticing the typo.
Len Brown, Intel Open Source Technology Center
next prev parent reply other threads:[~2015-05-01 21:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-19 0:53 [PATCH 0/1] speeding up cpu_up() Len Brown
2015-04-19 0:53 ` [PATCH 1/1] x86: replace cpu_up hard-coded mdelay with variable Len Brown
2015-04-20 7:13 ` Ingo Molnar
2015-04-20 12:37 ` Brown, Len
2015-04-20 17:45 ` Ingo Molnar
2015-04-22 5:40 ` Paul Gortmaker
2015-04-22 6:07 ` Ingo Molnar
2015-05-01 21:02 ` Len Brown [this message]
2015-04-20 7:15 ` [PATCH 0/1] speeding up cpu_up() Ingo Molnar
2015-05-01 21:42 ` Len Brown
2015-05-01 22:47 ` Borislav Petkov
2015-05-02 0:42 ` Aravind Gopalakrishnan
2015-05-03 16:13 ` Aravind Gopalakrishnan
2015-05-04 22:45 ` Aravind Gopalakrishnan
2015-05-05 7:15 ` Borislav Petkov
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=CAJvTdKnv8ibbu3NyQ4j62HbR7Sc92xF-DUQfsMuxGFf3-4Geiw@mail.gmail.com \
--to=lenb@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paul.gortmaker@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).