Re: [PATCH 1/2] multipath: clean up find_multipaths documentation

Xose Vazquez Perez <[email protected]> Fri, 17 Jul 2026 15:27:18 +0200
Newsgroups dev.linux.lists.dm-devel
Message-ID <[email protected]>
On 3/7/25 1:10 AM, Benjamin Marzinski wrote:

> The preferred term is "on" instead of "yes".
> 
> Signed-off-by: Benjamin Marzinski <[email protected]>
> ---
>   multipath/multipath.conf.5.in | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/multipath/multipath.conf.5.in b/multipath/multipath.conf.5.in
> index 0c1eff40..bdb6b605 100644
> --- a/multipath/multipath.conf.5.in
> +++ b/multipath/multipath.conf.5.in
> @@ -1214,7 +1214,7 @@ Both multipathd and multipath treat every non-blacklisted device as multipath
>   device path.
>   .TP
>   .I smart
> -This differs from \fIfind_multipaths yes\fR only in
> +This differs from \fIfind_multipaths on\fR only in
>   the way it treats new devices for which only one path has been
>   detected yet. When such a device is first encountered in udev rules, it is
>   treated as a multipath device. multipathd waits whether additional paths with

Could we please backport this patch to the stable-0.10.y and stable-0.11.y branches?

Thanks.