From: Zelin Deng <zelin.deng@linux.alibaba.com>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Petr Mladek <pmladek@suse.com>, Miroslav Benes <mbenes@suse.cz>,
shuah@kernel.org, linux-kselftest@vger.kernel.org,
live-patching@vger.kernel.org, mpdesouza@suse.com,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nsc@kernel.org>,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] selftests: livepatch: unset sub_make_done in case top level Makefile be overwritten
Date: Thu, 2 Jul 2026 16:09:14 +0800 [thread overview]
Message-ID: <b808a990-2bf7-4c6c-91c2-e8120fff03f5@linux.alibaba.com> (raw)
In-Reply-To: <20260702090852-9fe31739-3a7c-4604-9afa-805a6dcd8755@linutronix.de>
On 2026/7/2 15:11, Thomas Weißschuh wrote:
> On Thu, Jul 02, 2026 at 10:40:21AM +0800, Zelin Deng wrote:
>> 在 2026/7/1 23:19, Thomas Weißschuh 写道:
> (...)
:) Now client language has changed.
>> I had verify your proposal, it worked well - liveupatch kmod was built
>> successfully and top-level Makefile wasn't overwritten any more.
> Thanks for testing!
>
>> Petr thank you for your Ack, I think Thomas's proposal is better than mine,
>> we don't have to do the quirk everytime when new selftest kmod is added.
>>
>> Thomas, so do I have to send a updated patch or you will do it by youself?
> Your choice. You did most of the work, so should be credited as author.
> If you don't want I can do it, too.
Never mind, it will be good if you can do the change, so please do it
thank you. I'm just glad to report the issue and get some positive
feedbacks.
>
> Thomas
prev parent reply other threads:[~2026-07-02 8:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 8:37 [PATCH] selftests: livepatch: unset sub_make_done in case top level Makefile be overwritten Zelin Deng
2026-06-19 14:42 ` Miroslav Benes
2026-06-21 14:36 ` Zelin Deng
2026-06-30 14:32 ` Petr Mladek
2026-06-30 16:12 ` Thomas Weißschuh
2026-07-01 15:14 ` Petr Mladek
2026-07-01 15:19 ` Thomas Weißschuh
2026-07-02 2:40 ` Zelin Deng
2026-07-02 7:11 ` Thomas Weißschuh
2026-07-02 8:09 ` Zelin Deng [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=b808a990-2bf7-4c6c-91c2-e8120fff03f5@linux.alibaba.com \
--to=zelin.deng@linux.alibaba.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mpdesouza@suse.com \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=pmladek@suse.com \
--cc=shuah@kernel.org \
--cc=thomas.weissschuh@linutronix.de \
/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