From: Borislav Petkov <bp@alien8.de>
To: Len Brown <lenb@kernel.org>
Cc: X86 ML <x86@kernel.org>, Linux PM list <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Len Brown <len.brown@intel.com>
Subject: Re: [PATCH 2/2] x86: speed cpu_up by quirking cpu_init_udelay
Date: Fri, 8 May 2015 20:27:32 +0200 [thread overview]
Message-ID: <20150508182731.GF3904@pd.tnic> (raw)
In-Reply-To: <CAJvTdKk3TM1PMUgGeWCxThzVknfBc8xMK-dJkbxJrwkWhjGzLg@mail.gmail.com>
On Fri, May 08, 2015 at 02:15:42PM -0400, Len Brown wrote:
> I agree with you. Further, you made me think about it, and while it
> was helpful when I wrote the patch, I don't think any printk() is
> needed upstream.
Yeah, you're right.
If a user did override it with cpu_init_udelay, it'll be in
/proc/cmdline. And dmesg, and so on...
> see v3 just sent.
Looks ok.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2015-05-08 18:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 6:37 [PATCH 0/2 v2] speeding up cpu_up() Len Brown
2015-05-08 6:37 ` [PATCH 1/2] x86: replace cpu_up hard-coded mdelay with variable udelay Len Brown
2015-05-08 6:37 ` [PATCH 2/2] x86: speed cpu_up by quirking cpu_init_udelay Len Brown
2015-05-08 7:51 ` Ingo Molnar
2015-05-08 8:23 ` Borislav Petkov
2015-05-08 8:32 ` Borislav Petkov
2015-05-08 18:15 ` Len Brown
2015-05-08 18:27 ` Borislav Petkov [this message]
2015-05-09 7:22 ` Ingo Molnar
2015-05-09 7:24 ` Ingo Molnar
2015-05-09 8:04 ` 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=20150508182731.GF3904@pd.tnic \
--to=bp@alien8.de \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.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