From: Markus Elfring <Markus.Elfring@web.de>
To: Tiezhu Yang <yangtiezhu@loongson.cn>, 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>, Xuefeng Li <lixuefeng@loongson.cn>,
linux-kernel@vger.kernel.org
Subject: Re: [v2 1/4] selftests: kmod: Subsequent patch series with cover letters?
Date: Mon, 20 Apr 2020 14:12:02 +0200 [thread overview]
Message-ID: <716aa410-dd2f-f8d0-b3b6-5f26b42990dc@web.de> (raw)
In-Reply-To: <ac7bd076-8fb2-6d8b-655c-98ea7e7d2a4d@loongson.cn>
> OK, thanks for your suggestion.
Thanks for your acceptance.
> I will resend it with a cover letter.
I guess that such a resend would be needed only
if another version for this patch series will be published.
It seems that the attention can occasionally grow also for
the usage of helpful cover letters.
Regards,
Markus
prev parent reply other threads:[~2020-04-20 12:12 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
2020-04-20 12:12 ` 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=716aa410-dd2f-f8d0-b3b6-5f26b42990dc@web.de \
--to=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 \
--cc=yangtiezhu@loongson.cn \
/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
all inboxes | Powered by JetHome®