[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250407150124.GA12900@lst.de>
Date: Mon, 7 Apr 2025 17:01:24 +0200
From: Christoph Hellwig <hch@....de>
To: John Meneghini <jmeneghi@...hat.com>
Cc: Christoph Hellwig <hch@....de>, kbusch@...nel.org, sagi@...mberg.me,
loberman@...hat.com, linux-nvme@...ts.infradead.org,
linux-kernel@...r.kernel.org, emilne@...hat.com, bgurney@...hat.com
Subject: Re: [PATCH v2 2/3] nvme-multipath: add the NVME_MULTIPATH_PARAM
config option
On Fri, Apr 04, 2025 at 06:28:10PM -0400, John Meneghini wrote:
>> So maybe invert the option to
>>
>> config NVME_MULTIPATH_DISABLE
>> bool "Allow overriding the default nvme-multipath parameter"
>
> So the question is: do you want the core_nvme.multipath parameter
> to be excluded by default, or included by default?
I can live with it either way.
> Keith and I agreed to call this CONFIG_NVME_DISBALE_MULTIPATH_PARAM.
> However during testing I realized that many of the default make 'config'
> rules would end up with CONFIG_NVME_DISBALE_MULTIPATH_PARAM=y,
> even if I set the config rule to "default n".
>
> For example:
>
> make localmodconfig
> make allmodconfig
>
> would end up with compiling out the core_nvme.multipath parameter and I
> don't think this is what we want.
Weird, how does that override the explicit default statement?
> How about something simple like this:
>
> +config NVME_ENABLE_MULTIPATH_PARAM
> + bool "NVMe enable core_nvme.multipath param"
> + depends on NVME_CORE && NVME_MULTIPATH
> + default y
"default y" is the default, so it can be skipped.
Powered by blists - more mailing lists