From: Thomas Gleixner <tglx@linutronix.de>
To: Ingo Molnar <mingo@kernel.org>, linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>, Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH 2/2] entry: Correct 'noinstr' attributes
Date: Sun, 26 Jul 2020 15:39:43 +0200 [thread overview]
Message-ID: <877duqcs4g.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20200725091951.744848-3-mingo@kernel.org>
Ingo Molnar <mingo@kernel.org> writes:
> The noinstr attribute is to be specified before the return type in the
> same way 'inline' is used.
>
> Similar cases were recently fixed for x86, via:
>
> 7f6fa101dfac: ("x86: Correct noinstr qualifiers")
>
> These 2 cases were carried over by the new generic entry code.
Yes, my bad. I merged the above and then forgot to carry it over.
next prev parent reply other threads:[~2020-07-26 13:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-25 9:19 [PATCH 0/2] Fixes for the generic entry/exit framework Ingo Molnar
2020-07-25 9:19 ` [PATCH 1/2] entry: Fix CONFIG_SECCOMP assumption Ingo Molnar
2020-07-26 13:38 ` Thomas Gleixner
2020-07-26 17:47 ` Ingo Molnar
2020-07-27 13:39 ` Thomas Gleixner
2020-07-25 9:19 ` [PATCH 2/2] entry: Correct 'noinstr' attributes Ingo Molnar
2020-07-26 13:39 ` Thomas Gleixner [this message]
2020-07-26 13:47 ` [tip: core/entry] " tip-bot2 for Ingo Molnar
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=877duqcs4g.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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