From: Martin Wilck <mwilck@suse.com>
To: Muneendra Kumar <muneendra.kumar@broadcom.com>,
dm-devel@redhat.com, bmarzins@redhat.com
Cc: mkumar@redhat.com
Subject: Re: [dm-devel] [PATCH v2] multipathd: Added support to handle FPIN-Li events for FC-NVMe
Date: Thu, 21 Sep 2023 17:29:20 +0200 [thread overview]
Message-ID: <ebda40ae4b189ee2d6993d0ef2b1ca47aae34f3a.camel@suse.com> (raw)
In-Reply-To: <a628e5d3a414f0675ba3604f30e2545f5c392c20.camel@suse.com>
On Thu, 2023-09-21 at 16:09 +0200, Martin Wilck wrote:
> On Wed, 2023-09-20 at 20:41 -0700, Muneendra Kumar wrote:
> > From: Muneendra <muneendra.kumar@broadcom.com>
> >
> > This patch adds the support to handle FPIN-Li for FC-NVMe.
> > On receiving the FPIN-Li events this patch moves the devices
> > paths
> > which are affected due to link integrity to marginal path
> > groups.
> > The paths which are set to marginal path group will be unset
> > on receiving the RSCN events
> >
> > Signed-off-by: Muneendra <muneendra.kumar@broadcom.com>
> > Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
>
>
> Reviewed-by: Martin Wilck <mwilck@suse.com>
There was a minor compilation error for 32 bit architectures (%lx vs
%llx format specifier), which I've fixed on my queue branch:
https://github.com/openSUSE/multipath-tools/tree/queue
Regards,
Martin
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
prev parent reply other threads:[~2023-09-21 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 3:41 [dm-devel] [PATCH v2] multipathd: Added support to handle FPIN-Li events for FC-NVMe Muneendra Kumar
2023-09-21 14:09 ` Martin Wilck
2023-09-21 15:29 ` Martin Wilck [this message]
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=ebda40ae4b189ee2d6993d0ef2b1ca47aae34f3a.camel@suse.com \
--to=mwilck@suse.com \
--cc=bmarzins@redhat.com \
--cc=dm-devel@redhat.com \
--cc=mkumar@redhat.com \
--cc=muneendra.kumar@broadcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox