From: Kees Cook <kees@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>,
linux-kernel@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Benjamin Tissoires <bentiss@kernel.org>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
Janosch Frank <frankja@linux.ibm.com>,
Jiri Kosina <jikos@kernel.org>, Shuah Khan <shuah@kernel.org>,
bpf@vger.kernel.org, kvm@vger.kernel.org,
linux-input@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-rtc@vger.kernel.org
Subject: Re: [PATCH v2 0/2] selftests: harness: refactor __constructor_order
Date: Mon, 5 Aug 2024 21:27:23 -0700 [thread overview]
Message-ID: <202408052126.E8A8120C1@keescook> (raw)
In-Reply-To: <20240727143816.1808657-1-masahiroy@kernel.org>
On Sat, Jul 27, 2024 at 11:37:35PM +0900, Masahiro Yamada wrote:
>
> This series refactors __constructor_order because
> __constructor_order_last() is unneeded.
>
> No code change since v1.
> I reworded "reverse-order" to "backward-order" in commit description.
>
>
> Masahiro Yamada (2):
> selftests: harness: remove unneeded __constructor_order_last()
> selftests: harness: rename __constructor_order for clarification
Thanks for resending this!
Reviewed-by: Kees Cook <kees@kernel.org>
Shuah, do you want to take this via kselftest? If not, I can carry it...
-Kees
--
Kees Cook
next prev parent reply other threads:[~2024-08-06 4:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-27 14:37 [PATCH v2 0/2] selftests: harness: refactor __constructor_order Masahiro Yamada
2024-07-27 14:37 ` [PATCH v2 1/2] selftests: harness: remove unneeded __constructor_order_last() Masahiro Yamada
2024-08-06 4:27 ` Kees Cook [this message]
2024-08-06 19:36 ` [PATCH v2 0/2] selftests: harness: refactor __constructor_order Shuah Khan
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=202408052126.E8A8120C1@keescook \
--to=kees@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=bentiss@kernel.org \
--cc=borntraeger@linux.ibm.com \
--cc=bpf@vger.kernel.org \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=jikos@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=masahiroy@kernel.org \
--cc=shuah@kernel.org \
--cc=wad@chromium.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).