From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
pauld@redhat.com, longman@redhat.com,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Subject: Re: [PATCH] powerpc/shared: include correct header for static key
Date: Mon, 6 Jan 2020 16:23:23 +1100 (AEDT) [thread overview]
Message-ID: <47rkSD0mxYz9sR4@ozlabs.org> (raw)
In-Reply-To: <20191223133147.129983-1-Jason@zx2c4.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 789 bytes --]
On Mon, 2019-12-23 at 13:31:47 UTC, "Jason A. Donenfeld" wrote:
> Recently, the spinlock implementation grew a static key optimization,
> but the jump_label.h header include was left out, leading to build
> errors:
>
> linux/arch/powerpc/include/asm/spinlock.h:44:7: error: implicit declaration of function ‘static_branch_unlikely’ [-Werror=implicit-function-declaration]
> 44 | if (!static_branch_unlikely(&shared_processor))
>
> This commit adds the missing header.
>
> Fixes: 656c21d6af5d ("powerpc/shared: Use static key to detect shared processor")
> Cc: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
Applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c/6da3eced8c5f3b03340b0c395bacd552c4d52411
cheers
next prev parent reply other threads:[~2020-01-06 5:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 13:31 [PATCH] powerpc/shared: include correct header for static key Jason A. Donenfeld
2020-01-06 5:23 ` Michael Ellerman [this message]
[not found] <xagsmtp2.20191223133223.8837@vmsdvm3.vnet.ibm.com>
2019-12-24 16:22 ` Srikar Dronamraju
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=47rkSD0mxYz9sR4@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=Jason@zx2c4.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=longman@redhat.com \
--cc=pauld@redhat.com \
--cc=srikar@linux.vnet.ibm.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 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).