From: Markus Elfring <Markus.Elfring@web.de>
To: Kunwu Chan <chentao@kylinos.cn>, Will Deacon <will@kernel.org>,
linux-kselftest@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kernel-team@android.com,
Kunwu Chan <kunwu.chan@hotmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Muhammad Usama Anjum <usama.anjum@collabora.com>,
Shuah Khan <shuah@kernel.org>
Subject: Re: kselftest: arm64: Add a null pointer check
Date: Sun, 28 Apr 2024 17:38:35 +0200 [thread overview]
Message-ID: <d3f389e2-7a72-4ce0-9f05-245c4f34f829@web.de> (raw)
In-Reply-To: <171429017935.1716809.10906291781915903062.b4-ty@kernel.org>
> > There is a 'malloc' call, which can be unsuccessful.
> > This patch will add the malloc failure checking
> > to avoid possible null dereference and give more information
> > about test fail reasons.
>
> Applied to arm64 (for-next/selftests), thanks!
>
> [1/1] kselftest: arm64: Add a null pointer check
> https://git.kernel.org/arm64/c/80164282b362
Why did you not adhere to known requirements for such a change description?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.9-rc5#n94
* Imperative mood
* Addition of the tag “Fixes”
Regards,
Markus
prev parent reply other threads:[~2024-04-28 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 8:21 [PATCH] kselftest: arm64: Add a null pointer check Kunwu Chan
2024-04-23 8:42 ` Muhammad Usama Anjum
2024-04-23 9:00 ` Markus Elfring
2024-04-28 8:59 ` Will Deacon
2024-04-28 15:38 ` Markus Elfring [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=d3f389e2-7a72-4ce0-9f05-245c4f34f829@web.de \
--to=markus.elfring@web.de \
--cc=catalin.marinas@arm.com \
--cc=chentao@kylinos.cn \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel-team@android.com \
--cc=kunwu.chan@hotmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=usama.anjum@collabora.com \
--cc=will@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 read-only IMAP folder(s) and NNTP newsgroup(s).