From: Dev Jain <dev.jain@arm.com>
To: Alok Tiwari <alok.a.tiwari@oracle.com>,
shuah@kernel.org, broonie@kernel.org,
linux-kselftest@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests: fix typo in ss_flags check message for sas.c
Date: Tue, 26 Aug 2025 10:00:14 +0530 [thread overview]
Message-ID: <d11aa803-058b-4585-bcee-a6664cf049a9@arm.com> (raw)
In-Reply-To: <20250824191721.631980-1-alok.a.tiwari@oracle.com>
On 25/08/25 12:47 am, Alok Tiwari wrote:
> Fix a typo in the signal alternate stack test where the error
> message incorrectly used tss_flags instead of the correct field
> name ss_flags.
>
> This change ensures the test output accurately reflects the
> structure member being checked.
>
> Signed-off-by: Alok Tiwari <alok.a.tiwari@oracle.com>
> ---
>
Reviewed-by: Dev Jain <dev.jain@arm.com>
prev parent reply other threads:[~2025-08-26 4:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-24 19:17 [PATCH] selftests: fix typo in ss_flags check message for sas.c Alok Tiwari
2025-08-25 15:38 ` Mark Brown
2025-08-26 4:30 ` Dev Jain [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=d11aa803-058b-4585-bcee-a6664cf049a9@arm.com \
--to=dev.jain@arm.com \
--cc=alok.a.tiwari@oracle.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@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).