From: Heiko Carstens <hca@linux.ibm.com>
To: Ilya Leoshkevich <iii@linux.ibm.com>
Cc: Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-s390@vger.kernel.org
Subject: Re: [PATCH 0/2] s390/preempt: mark all functions __always_inline
Date: Thu, 21 Mar 2024 07:45:05 +0100 [thread overview]
Message-ID: <20240321064505.8101-A-hca@linux.ibm.com> (raw)
In-Reply-To: <20240320230007.4782-1-iii@linux.ibm.com>
On Wed, Mar 20, 2024 at 11:47:47PM +0100, Ilya Leoshkevich wrote:
> Hi,
>
> This series marks all functions in asm/atomic_ops.h, asm/atomic.h and
> asm/preempt.h __always_inline, and is based on the discussion with Mark
> [1]. It's one of the changes required to unbreak the work-in-progress
> KMSAN support on s390x after commit 5ec8e8ea8b77 ("mm/sparsemem: fix
> race in accessing memory_section->usage"). But it also makes sense on
> its own, and may prevent issues with the other sanitizers in the
> future.
...
> Ilya Leoshkevich (2):
> s390/atomic: mark all functions __always_inline
> s390/preempt: mark all functions __always_inline
>
> arch/s390/include/asm/atomic.h | 44 +++++++++++++++---------------
> arch/s390/include/asm/atomic_ops.h | 22 +++++++--------
> arch/s390/include/asm/preempt.h | 36 ++++++++++++------------
> 3 files changed, 51 insertions(+), 51 deletions(-)
Applied, thanks!
prev parent reply other threads:[~2024-03-21 6:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 22:47 [PATCH 0/2] s390/preempt: mark all functions __always_inline Ilya Leoshkevich
2024-03-20 22:47 ` [PATCH 1/2] s390/atomic: " Ilya Leoshkevich
2024-03-20 22:47 ` [PATCH 2/2] s390/preempt: " Ilya Leoshkevich
2024-03-21 6:45 ` Heiko Carstens [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=20240321064505.8101-A-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=svens@linux.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 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.