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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2025-03-06 at 19:10 -0500, Benjamin Marzinski wrote:
> The preferred term is "on" instead of "yes".
> 
> Signed-off-by: Benjamin Marzinski <bmarzins@xxxxxxxxxx>

Reviewed-by: Martin Wilck <mwilck@xxxxxxxx>

> ---
>  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






[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux