From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Markus Elfring <Markus.Elfring@web.de>, linux-kselftest@vger.kernel.org
Cc: Luis Chamberlain <mcgrof@kernel.org>,
Shuah Khan <shuah@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jessica Yu <jeyu@kernel.org>,
linux-kernel@vger.kernel.org, Xuefeng Li <lixuefeng@loongson.cn>
Subject: Re: [PATCH v2 1/4] selftests: kmod: Use variable NAME in kmod_test_0001()
Date: Mon, 20 Apr 2020 19:40:52 +0800 [thread overview]
Message-ID: <ac7bd076-8fb2-6d8b-655c-98ea7e7d2a4d@loongson.cn> (raw)
In-Reply-To: <ff9ef06c-0607-8b8e-b80d-6a531921a67e@web.de>
On 04/20/2020 07:30 PM, Markus Elfring wrote:
>> Use the variable NAME instead of "\000" directly in kmod_test_0001().
> Would this patch series have been a bit nicer together with
> a cover letter?
OK, thanks for your suggestion. I will resend it with a cover letter.
Thanks,
Tiezhu Yang
>
> Regards,
> Markus
next prev parent reply other threads:[~2020-04-20 11:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 11:22 [PATCH v2 1/4] selftests: kmod: Use variable NAME in kmod_test_0001() Tiezhu Yang
2020-04-20 11:23 ` [PATCH v2 2/4] kmod: Remove redundant "be an" in the comment Tiezhu Yang
2020-04-20 11:23 ` [PATCH v2 3/4] kmod: Return directly if module name is empty in request_module() Tiezhu Yang
2020-04-20 11:23 ` [PATCH v2 4/4] test_kmod: Avoid potential double free in trigger_config_run_type() Tiezhu Yang
2020-04-20 11:30 ` [PATCH v2 1/4] selftests: kmod: Use variable NAME in kmod_test_0001() Markus Elfring
2020-04-20 11:40 ` Tiezhu Yang [this message]
2020-04-20 12:12 ` [v2 1/4] selftests: kmod: Subsequent patch series with cover letters? Markus Elfring
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=ac7bd076-8fb2-6d8b-655c-98ea7e7d2a4d@loongson.cn \
--to=yangtiezhu@loongson.cn \
--cc=Markus.Elfring@web.de \
--cc=akpm@linux-foundation.org \
--cc=jeyu@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--cc=mcgrof@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).