From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Subject: Re: powerpc/64: Don't use early_cpu_has_feature() in cpu_ready_for_interrupts()
Date: Fri, 31 Mar 2017 23:33:53 +1100 (AEDT) [thread overview]
Message-ID: <3vvgsY3mC3z9s2s@ozlabs.org> (raw)
In-Reply-To: <1490073878-5900-1-git-send-email-mpe@ellerman.id.au>
On Tue, 2017-03-21 at 05:24:38 UTC, Michael Ellerman wrote:
> cpu_ready_for_interrupts() is called after feature patching, so there's
> no need to use early_cpu_has_feature().
>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Applied to powerpc next.
https://git.kernel.org/powerpc/c/5511a45fc134f0784c403ef3488e2c
cheers
prev parent reply other threads:[~2017-03-31 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 5:24 [PATCH] powerpc/64: Don't use early_cpu_has_feature() in cpu_ready_for_interrupts() Michael Ellerman
2017-03-31 12:33 ` Michael Ellerman [this message]
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=3vvgsY3mC3z9s2s@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).