From: Andrew Morton <akpm@linux-foundation.org>
To: Uladzislau Rezki <urezki@gmail.com>
Cc: ally heev <allyheev@gmail.com>,
skhan@linuxfoundation.org, david@redhat.com, shuah@kernel.org,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kselftest: mm: fix typos in test_vmalloc.sh
Date: Sun, 24 Aug 2025 17:17:22 -0700 [thread overview]
Message-ID: <20250824171722.ea915592ea3bd060c6b17a38@linux-foundation.org> (raw)
In-Reply-To: <aKq25rlqbyYDaWVo@pc636>
On Sun, 24 Aug 2025 08:53:26 +0200 Uladzislau Rezki <urezki@gmail.com> wrote:
> > run_stability_check()
> > @@ -160,7 +160,7 @@ function run_test()
> > usage
> > else
> > if [[ "$1" = "performance" ]]; then
> > - run_perfformance_check
> > + run_performance_check
> > elif [[ "$1" = "stress" ]]; then
> > run_stability_check
> > elif [[ "$1" = "smoke" ]]; then
> > --
> > 2.34.1
> >
> >
> ./scripts/checkpatch.pl ./0001-kselftest-mm-fix-typos-in-test_vmalloc.sh.patch
> WARNING: Missing commit description - Add an appropriate one
>
> total: 0 errors, 1 warnings, 24 lines checked
>
> NOTE: For some of the reported defects, checkpatch may be able to
> mechanically convert to the typical style using --fix or --fix-inplace.
>
> ./0001-kselftest-mm-fix-typos-in-test_vmalloc.sh.patch has style problems, please review.
>
> NOTE: If any of the errors are false positives, please report
> them to the maintainer, see CHECKPATCH in MAINTAINERS.
>
> Can you add a commit message?
A changelog would be identical to the subject. checkpatch is being a
bit excessive here.
Oh well, I'll add the obvious text.
next prev parent reply other threads:[~2025-08-25 0:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-23 17:02 [PATCH] kselftest: mm: fix typos in test_vmalloc.sh ally heev
2025-08-24 6:53 ` Uladzislau Rezki
2025-08-25 0:17 ` Andrew Morton [this message]
2025-08-25 2:53 ` ally heev
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=20250824171722.ea915592ea3bd060c6b17a38@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=allyheev@gmail.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=urezki@gmail.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;
as well as URLs for NNTP newsgroup(s).