All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Wilck <mwilck@suse.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: Benjamin Marzinski <bmarzins@redhat.com>,
	Christophe Varoqui <christophe.varoqui@opensvc.com>,
	DM_DEVEL-ML <dm-devel@lists.linux.dev>
Subject: Re: [PATCH 2/5] multipath-tools: clarify path selector descriptions in multipath.conf.5
Date: Mon, 15 Jun 2026 10:37:58 +0200	[thread overview]
Message-ID: <35ab9802b0e8a55ade753048cb70ffcafe1069a4.camel@suse.com> (raw)
In-Reply-To: <994b66b1-68fb-4dd6-90e4-8fcd6f894f62@gmail.com>

On Mon, 2026-06-15 at 10:26 +0200, Xose Vazquez Perez wrote:
> On 6/15/26 10:16 AM, Martin Wilck wrote:
> 
> > On Sat, 2026-06-13 at 15:09 +0200, Xose Vazquez Perez wrote:
> > > Selectors operate on the next individual I/O request rather
> > > than a "bunch" of I/O.
> > 
> > This patch doesn't apply cleanly to any of my branches (master,
> > queue,
> > tip).
> That quote is from the patch series I sent earlier. You might have
> missed it:

No, but Ben had remarks on it, and I expected you to submit a v2.
So I am gathering that you want me to apply that series, and Ben's
points are addressed by the 2nd series on top. That wasn's obvious to
me, sorry.

Martin


> 
> Xose Vazquez Perez (3):
>    multipath-tools: delete obsolete information from multipath.conf.5
>    multipath-tools: remove explicit width from .TP macros in
> multipath.conf.5
>    multipath-tools: remove explicit widths from macros in the
> remaining man pages
> 
>   libmpathpersist/mpath_persistent_reserve_in.3 |   4 +-
>   .../mpath_persistent_reserve_out.3            |   4 +-
>   mpathpersist/mpathpersist.8.in                |   2 +-
>   multipath/multipath.8.in                      |   6 +-
>   multipath/multipath.conf.5.in                 | 135 +++++----------
> ---
>   multipathd/multipathd.8.in                    |   9 +-
>   6 files changed, 51 insertions(+), 109 deletions(-)

  reply	other threads:[~2026-06-15  8:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-13 13:09 [PATCH 0/5] multipath-tools: clean up man pages II Xose Vazquez Perez
2026-06-13 13:09 ` [PATCH 1/5] multipath-tools: remove syntax check comments from man pages Xose Vazquez Perez
2026-06-13 13:09 ` [PATCH 2/5] multipath-tools: clarify path selector descriptions in multipath.conf.5 Xose Vazquez Perez
2026-06-15  8:16   ` Martin Wilck
2026-06-15  8:26     ` Xose Vazquez Perez
2026-06-15  8:37       ` Martin Wilck [this message]
2026-06-15  9:15       ` Martin Wilck
2026-06-15 16:44         ` Xose Vazquez Perez
2026-06-15 17:08           ` Martin Wilck
2026-06-15  8:18   ` Martin Wilck
2026-06-13 13:09 ` [PATCH 3/5] multipath-tools: specify file paths using variables and add FILES section " Xose Vazquez Perez
2026-06-13 13:09 ` [PATCH 4/5] multipath-tools: clarify user_friendly_names prefix behavior " Xose Vazquez Perez
2026-06-15  8:15   ` Martin Wilck
2026-06-13 13:10 ` [PATCH 5/5] multipath-tools: fix mandoc errors/warnings in man pages Xose Vazquez Perez

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=35ab9802b0e8a55ade753048cb70ffcafe1069a4.camel@suse.com \
    --to=mwilck@suse.com \
    --cc=bmarzins@redhat.com \
    --cc=christophe.varoqui@opensvc.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=xose.vazquez@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.