From: Dev Jain <dev.jain@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: shuah@kernel.org, oleg@redhat.com, stsp2@yandex.ru,
mingo@kernel.org, tglx@linutronix.de, mark.rutland@arm.com,
ryan.roberts@arm.com, suzuki.poulose@arm.com,
Anshuman.Khandual@arm.com, DeepakKumar.Mishra@arm.com,
AneeshKumar.KizhakeVeetil@arm.com,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] selftests: Rename sigaltstack to generic signal
Date: Tue, 11 Jun 2024 16:32:05 +0530 [thread overview]
Message-ID: <a154a0e1-c7e7-4818-96ec-9cbb42734ef0@arm.com> (raw)
In-Reply-To: <ZmgtA_GW_GPgPM1E@finisterre.sirena.org.uk>
On 6/11/24 16:24, Mark Brown wrote:
> On Tue, Jun 11, 2024 at 01:26:49PM +0530, Dev Jain wrote:
>> Rename sigaltstack to signal, and rename the existing test to
>> sigaltstack.c.
>>
>> Signed-off-by: Dev Jain <dev.jain@arm.com>
>> ---
> If people review patches and give a tag for them you should carry the
> tag forward to avoid having to duplicate the review. From v1:
>
> I think this is reasonable if we're going to add more generic signal
> tests - sigaltstack is a fairly small bit of functionality and having it
> covered as part of a broader signal suite and the overhead of setting up
> the suite separately is probably not worth it.
>
> Reviewed-by: Mark Brown <broonie@kernel.org>
Ah yes, I did know it, I forgot. Shall take care.
next prev parent reply other threads:[~2024-06-11 11:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 7:56 [PATCH v2 0/2] Add test to distinguish between thread's signal mask and ucontext_t Dev Jain
2024-06-11 7:56 ` [PATCH v2 1/2] selftests: Rename sigaltstack to generic signal Dev Jain
2024-06-11 10:54 ` Mark Brown
2024-06-11 11:02 ` Dev Jain [this message]
2024-06-11 7:56 ` [PATCH v2 2/2] selftests: Add a test mangling with uc_sigmask Dev Jain
2024-06-11 11:25 ` Mark Brown
2024-06-12 4:44 ` Dev Jain
2024-06-12 13:16 ` Mark Brown
2024-06-13 4:51 ` Dev Jain
2024-06-13 9:19 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2024-06-11 7:43 [PATCH v2 0/2] Add test to distinguish between thread's signal mask and ucontext_t Dev Jain
2024-06-11 7:43 ` [PATCH v2 1/2] selftests: Rename sigaltstack to generic signal Dev Jain
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=a154a0e1-c7e7-4818-96ec-9cbb42734ef0@arm.com \
--to=dev.jain@arm.com \
--cc=AneeshKumar.KizhakeVeetil@arm.com \
--cc=Anshuman.Khandual@arm.com \
--cc=DeepakKumar.Mishra@arm.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=stsp2@yandex.ru \
--cc=suzuki.poulose@arm.com \
--cc=tglx@linutronix.de \
/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