Message ID | 1587452704-1299-1-git-send-email-yangtiezhu@loongson.cn (mailing list archive) |
---|---|
Headers | show |
Series | Fix some issues about kmod | expand |
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/ Thanks, Tiezhu Yang
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
On Mon, May 11, 2020 at 12:28 PM Luis Chamberlain <mcgrof@kernel.org> wrote: > > 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. I'll pick these up, and run tests now that I have a finalized solution in place for the patch replacement I mentioned which was needed. Sorry this took so long, but I am glad I took my time. I'll post soon after I test the new fix. Luis