From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [1/3] powerpc: Don't preempt_disable() in show_cpuinfo()
Date: Mon, 15 Jan 2018 21:16:12 +1100 (AEDT) [thread overview]
Message-ID: <3zKq4z1Cbcz9sCZ@ozlabs.org> (raw)
In-Reply-To: <20180110061014.29181-1-benh@kernel.crashing.org>
On Wed, 2018-01-10 at 06:10:12 UTC, Benjamin Herrenschmidt wrote:
> This causes warnings from cpufreq mutex code. This is also
> rather unnecessary and ineffective. If we really want to
> prevent concurrent unplug, we could take the unplug read
> lock but I don't see this being critical.
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c/349524bc0da698ec77f2057cf4a494
cheers
next prev parent reply other threads:[~2018-01-15 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 6:10 [PATCH 1/3] powerpc: Don't preempt_disable() in show_cpuinfo() Benjamin Herrenschmidt
2018-01-10 6:10 ` [PATCH 2/3] powerpc: Make newline in cpuinfo unconditional Benjamin Herrenschmidt
2018-01-17 13:30 ` [2/3] " Michael Ellerman
2018-01-10 6:10 ` [PATCH 3/3] powerpc: Cosmetic cleanup of cpuinfo_op Benjamin Herrenschmidt
2018-01-17 13:30 ` [3/3] " Michael Ellerman
2018-01-15 10:16 ` Michael Ellerman [this message]
2018-01-17 13:25 ` [1/3] powerpc: Don't preempt_disable() in show_cpuinfo() Michael Ellerman
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=3zKq4z1Cbcz9sCZ@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.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).