From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: linuxppc-dev@lists.ozlabs.org, john.ogness@linutronix.de,
frank.rowand@sony.com, clg@kaod.org, nick.child@ibm.com,
linux-kernel@vger.kernel.org, lance@osuosl.org,
christophe.leroy@csgroup.eu, rcu@vger.kernel.org,
adobriyan@gmail.com, benh@kernel.crashing.org, paulus@samba.org,
robh@kernel.org, mpe@ellerman.id.au, paulmck@kernel.org,
zhouzhouyi@gmail.com, npiggin@gmail.com
Subject: Re: [PATCH linux-next v2] powerpc: init jump label early in ppc 64
Date: Tue, 02 Aug 2022 21:02:25 +1000 [thread overview]
Message-ID: <165943814554.1061647.998228378866777067.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20220726015747.11754-1-zhouzhouyi@gmail.com>
On Tue, 26 Jul 2022 09:57:47 +0800, zhouzhouyi@gmail.com wrote:
> From: Zhouyi Zhou <zhouzhouyi@gmail.com>
>
> In ppc 64, invoke jump_label_init in setup_feature_keys is too late
> because static key will be used in subroutine of parse_early_param
> which is again subroutine of early_init_devtree.
>
> So we invoke jump_label_init just before parse_early_param in
> early_init_devtree.
>
> [...]
Applied to powerpc/next.
[1/1] powerpc: init jump label early in ppc 64
https://git.kernel.org/powerpc/c/ca829e05d3d4f728810cc5e4b468d9ebc7745eb3
cheers
next prev parent reply other threads:[~2022-08-02 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 1:57 [PATCH linux-next v2] powerpc: init jump label early in ppc 64 zhouzhouyi
2022-08-02 11:02 ` Michael Ellerman [this message]
2022-08-06 6:45 ` 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=165943814554.1061647.998228378866777067.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=adobriyan@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@csgroup.eu \
--cc=clg@kaod.org \
--cc=frank.rowand@sony.com \
--cc=john.ogness@linutronix.de \
--cc=lance@osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=nick.child@ibm.com \
--cc=npiggin@gmail.com \
--cc=paulmck@kernel.org \
--cc=paulus@samba.org \
--cc=rcu@vger.kernel.org \
--cc=robh@kernel.org \
--cc=zhouzhouyi@gmail.com \
/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.