All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Marzinski <bmarzins@redhat.com>
To: Martin Wilck <martin.wilck@suse.com>
Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>,
	device-mapper development <dm-devel@lists.linux.dev>,
	Nitin Yewale <nyewale@redhat.com>
Subject: Re: [PATCH 3/7] libmultipath: print all values in snprint_failback
Date: Wed, 29 May 2024 11:03:09 -0400	[thread overview]
Message-ID: <ZldDrafYc1riyz76@redhat.com> (raw)
In-Reply-To: <5e534cd7c8034436819ef451e451fe00549d8a72.camel@suse.com>

On Fri, May 24, 2024 at 03:43:44PM +0200, Martin Wilck wrote:
> On Mon, 2024-05-13 at 13:36 -0400, Benjamin Marzinski wrote:
> > Add the missing output for manual failback and print the defferral
> > time
> > for deferred failbacks, if one isn't currently in progress.
> > 
> > Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
> > ---
> >  libmultipath/print.c | 6 +++++-
> >  1 file changed, 5 insertions(+), 1 deletion(-)
> > 
> > diff --git a/libmultipath/print.c b/libmultipath/print.c
> > index 89813517..14e7e325 100644
> > --- a/libmultipath/print.c
> > +++ b/libmultipath/print.c
> > @@ -218,9 +218,13 @@ snprint_failback (struct strbuf *buff, const
> > struct multipath * mpp)
> >  		return append_strbuf_str(buff, "immediate");
> >  	if (mpp->pgfailback == -FAILBACK_FOLLOWOVER)
> >  		return append_strbuf_str(buff, "followover");
> > +	if (mpp->pgfailback == -FAILBACK_MANUAL)
> > +		return append_strbuf_str(buff, "manual");
> > +	if (mpp->pgfailback == FAILBACK_UNDEF)
> > +		return append_strbuf_str(buff, "undef");
> >  
> >  	if (!mpp->failback_tick)
> > -		return append_strbuf_str(buff, "-");
> > +		return print_strbuf(buff, "%i", mpp->pgfailback);
> 
> Perhaps we should print something like "delayed:%i" here?

Sure.

> 
> Martin
> 
> 
> 
> >  	else
> >  		return snprint_progress(buff, mpp->failback_tick,
> >  					mpp->pgfailback);


  reply	other threads:[~2024-05-29 15:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13 17:36 [PATCH 0/7] multipath-tools man pages: add missing information Benjamin Marzinski
2024-05-13 17:36 ` [PATCH 1/7] libmultipath: remove pathgroup wildcard options Benjamin Marzinski
2024-05-13 17:36 ` [PATCH 2/7] multipath-tools man pages: don't assume multipath.socket is enabled Benjamin Marzinski
2024-05-13 17:36 ` [PATCH 3/7] libmultipath: print all values in snprint_failback Benjamin Marzinski
2024-05-24 13:43   ` Martin Wilck
2024-05-29 15:03     ` Benjamin Marzinski [this message]
2024-05-13 17:36 ` [PATCH 4/7] multipathd: Stop double counting map failures for no_path_retry > 0 Benjamin Marzinski
2024-05-13 17:36 ` [PATCH 5/7] multipath-tools man pages: add missing multipathd commands Benjamin Marzinski
2024-05-13 17:36 ` [PATCH 6/7] libmultipath: change the vend/prod/rev printing Benjamin Marzinski
2024-05-13 17:36 ` [PATCH 7/7] multipath-tools man pages: Add format wildcard descriptions Benjamin Marzinski
2024-05-13 19:11   ` Benjamin Marzinski
2024-05-24 14:29     ` Martin Wilck
2024-05-29 15:06       ` Benjamin Marzinski
2024-05-24 14:27   ` Martin Wilck
2024-05-29 15:15     ` Benjamin Marzinski
2024-05-24 14:28 ` [PATCH 0/7] multipath-tools man pages: add missing information Martin Wilck

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=ZldDrafYc1riyz76@redhat.com \
    --to=bmarzins@redhat.com \
    --cc=christophe.varoqui@opensvc.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=martin.wilck@suse.com \
    --cc=nyewale@redhat.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.