public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Yanjun.Zhu" <yanjun.zhu@linux.dev>
To: Pratyush Yadav <pratyush@kernel.org>
Cc: pasha.tatashin@soleen.com, rppt@kernel.org, shuah@kernel.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 1/1] selftests/liveupdate: Cleanup kernel optio CONFIG_LIVEUPDATE_TEST
Date: Tue, 10 Feb 2026 10:15:07 -0800	[thread overview]
Message-ID: <51f77faa-5d8b-4e8b-8cfd-04ae06726864@linux.dev> (raw)
In-Reply-To: <2vxz4inou3da.fsf@kernel.org>


On 2/10/26 5:36 AM, Pratyush Yadav wrote:
> On Thu, Jan 29 2026, Zhu Yanjun wrote:
>
>> 在 2026/1/29 20:28, Zhu Yanjun 写道:
>>> The kernel option CONFIG_LIVEUPDATE_TEST does not exist currently.
>>> Remove it.
>> In kernel 6.19-rc7, this kernel option still exists in the file
>>
>> tools/testing/selftests/liveupdate/config. Thus I send out this commit to remove
>> it.
> Yes, but the patch to add the config is in mm-nonmm-unstable. I am not
> sure if this worth the churn of removing this and re-adding it when that
> patch lands later. Do you see a real problem with this?
Thanks for the feedback.

I understand that the patch adding this functionality is currently in 
mm-nonmm-unstable. My concern was primarily adhering to the 
documentation, which suggests keeping the kernel configs pruned of 
unused options to avoid confusion for those running selftests.

However, I see your point regarding the churn. If you prefer, we can 
wait until the mm-nonmm-unstable branch is merged into the mainline. 
Once that happens, if this option remains truly redundant or if the 
implementation changes, I can resubmit the cleanup then.

Does that sound like a reasonable compromise to you?

Best regards,

Yanjun.Zhu

>
> [...]
>

  reply	other threads:[~2026-02-10 18:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-30  4:28 [PATCH 1/1] selftests/liveupdate: Cleanup kernel optio CONFIG_LIVEUPDATE_TEST Zhu Yanjun
2026-01-30  4:31 ` Zhu Yanjun
2026-02-10 13:36   ` Pratyush Yadav
2026-02-10 18:15     ` Yanjun.Zhu [this message]
2026-02-12 13:01       ` Pratyush Yadav

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=51f77faa-5d8b-4e8b-8cfd-04ae06726864@linux.dev \
    --to=yanjun.zhu@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=pratyush@kernel.org \
    --cc=rppt@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