From: Luis Chamberlain <mcgrof@kernel.org>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: akpm@linux-foundation.org, jeyu@kernel.org, shuah@kernel.org,
Markus.Elfring@web.de, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, lixuefeng@loongson.cn
Subject: Re: [PATCH v4 0/4] Fix some issues about kmod
Date: Mon, 11 May 2020 18:28:14 +0000 [thread overview]
Message-ID: <20200511182814.GS11244@42.do-not-panic.com> (raw)
In-Reply-To: <9b50d2b1-2fb4-10a1-5966-5458507a9b05@loongson.cn>
On Mon, May 11, 2020 at 08:59:37PM +0800, Tiezhu Yang wrote:
> Hi,
>
> Could you please apply the following three patches?
>
> [v4,1/4] selftests: kmod: Use variable NAME in kmod_test_0001()
> https://lore.kernel.org/patchwork/patch/1227980/
>
> [v4,2/4] kmod: Remove redundant "be an" in the comment
> https://lore.kernel.org/patchwork/patch/1227982/
>
> [v4,4/4] test_kmod: Avoid potential double free in trigger_config_run_type()
> https://lore.kernel.org/patchwork/patch/1227978/
Andrew,
These 3 patches should be fine.
I am re-working a replacement proper fix for patch #3, that requires a
change to the umh. I'll try to iron this out today.
Luis
next prev parent reply other threads:[~2020-05-11 18:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 7:05 [PATCH v4 0/4] Fix some issues about kmod Tiezhu Yang
2020-04-21 7:05 ` [PATCH v4 1/4] selftests: kmod: Use variable NAME in kmod_test_0001() Tiezhu Yang
2020-04-21 7:05 ` [PATCH v4 2/4] kmod: Remove redundant "be an" in the comment Tiezhu Yang
2020-04-21 7:05 ` [PATCH v4 3/4] kmod: Return directly if module name is empty in request_module() Tiezhu Yang
2020-04-22 8:32 ` Luis Chamberlain
2020-04-21 7:05 ` [PATCH v4 4/4] test_kmod: Avoid potential double free in trigger_config_run_type() Tiezhu Yang
2020-05-11 12:59 ` [PATCH v4 0/4] Fix some issues about kmod Tiezhu Yang
2020-05-11 18:28 ` Luis Chamberlain [this message]
2020-06-10 2:33 ` Luis Chamberlain
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=20200511182814.GS11244@42.do-not-panic.com \
--to=mcgrof@kernel.org \
--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=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