From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, clang-built-linux@googlegroups.com,
"ndesaulniers@google.com" <ndesaulniers@google.com>,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Subject: Re: [PATCH 4.19] include/linux/compiler*.h: define asm_volatile_goto
Date: Mon, 3 Jun 2019 09:58:16 +0200 [thread overview]
Message-ID: <20190603075816.GC7814@kroah.com> (raw)
In-Reply-To: <20190531055633.123516-1-natechancellor@gmail.com>
On Thu, May 30, 2019 at 10:56:34PM -0700, Nathan Chancellor wrote:
> From: "ndesaulniers@google.com" <ndesaulniers@google.com>
>
> commit 8bd66d147c88bd441178c7b4c774ae5a185f19b8 upstream.
>
> asm_volatile_goto should also be defined for other compilers that support
> asm goto.
>
> Fixes commit 815f0ddb346c ("include/linux/compiler*.h: make compiler-*.h
> mutually exclusive").
>
> Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>
> Signed-off-by: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
> Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
> ---
>
> Hi Greg and Sasha,
>
> Please pick up this patch for 4.19. It turns out that commit
> 13aceef06adf ("arm64: jump_label.h: use asm_volatile_goto macro instead
> of "asm goto"") was backported without this, which causes a build
> failure on arm64. This wasn't uncovered until now because clang didn't
> support asm goto so this code wasn't being compiled. Thankfully, that
> should change very soon :)
Now applied, thanks.
greg k-h
prev parent reply other threads:[~2019-06-03 7:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 5:56 [PATCH 4.19] include/linux/compiler*.h: define asm_volatile_goto Nathan Chancellor
2019-06-03 7:58 ` Greg Kroah-Hartman [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=20190603075816.GC7814@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=clang-built-linux@googlegroups.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=sashal@kernel.org \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).