From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Heiko Carstens <hca@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH v2 2/2] s390/signal: Cleanup coding style
Date: Wed, 14 Oct 2026 14:27:45 +0200 [thread overview]
Message-ID: <f51e6630-080d-4eb6-9d28-51e177b00c30@linux.ibm.com> (raw)
In-Reply-To: <20261013133453.2288894-3-hca@linux.ibm.com>
On 10/13/26 15:34, Heiko Carstens wrote:
> Only whitespace, comment, indentation and other trivial changes to
> adopt signal.c to current coding style.
>
> No functional change.
>
> Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
> ---
> arch/s390/kernel/signal.c | 224 +++++++++++++++-----------------------
> 1 file changed, 90 insertions(+), 134 deletions(-)
[...]
> @@ -257,94 +249,76 @@ SYSCALL_DEFINE0(rt_sigreturn)
> return 0;
> }
>
> -/*
> - * Determine which stack to use..
> - */
> -static inline void __user *
> -get_sigframe(struct k_sigaction *ka, struct pt_regs * regs, size_t frame_size)
> +/* Determine which stack to use. */
> +static inline void __user *get_sigframe(struct k_sigaction *ka, struct pt_regs *regs, size_t frame_size)
Checkpatch complains: this is now longer than 100 characters.
[...]
Otherwise:
Reviewed-by: Ilya Leoshkevich <iii@linux.ibm.com>
prev parent reply other threads:[~2026-10-14 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 13:34 [PATCH v2 0/2] s390/signal: Fix return address handling + cleanup Heiko Carstens
2026-10-13 13:34 ` [PATCH v2 1/2] s390/signal: Fix incorrect return address in signal frame Heiko Carstens
2026-10-13 13:43 ` sashiko-bot
2026-10-13 13:34 ` [PATCH v2 2/2] s390/signal: Cleanup coding style Heiko Carstens
2026-10-13 13:49 ` sashiko-bot
2026-10-14 12:27 ` Ilya Leoshkevich [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=f51e6630-080d-4eb6-9d28-51e177b00c30@linux.ibm.com \
--to=iii@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox