From: snitzer@redhat.com (Mike Snitzer)
Subject: nvmet_fc: correct broken add_port
Date: Fri, 22 Dec 2017 11:41:13 -0500 [thread overview]
Message-ID: <20171222164113.GA31385@redhat.com> (raw)
In-Reply-To: <079257ac-fc03-d28e-3906-7a584b5bee4a@broadcom.com>
On Fri, Dec 22 2017 at 10:50am -0500,
James Smart <james.smart@broadcom.com> wrote:
> On 12/21/2017 11:23 PM, Johannes Thumshirn wrote:
> >But a Fixes: and/or Cc: <stable at vger.kernel.org> might have been a
> >good Idea as well.
> >
>
> Fixes perhaps.? The patch that introduced the issue
> (a0b69cc8e5caff3cb6442dfa807f47b44e716aad) is only in nvme-4.16, so
> it doesn't quite apply.
Right, a Fixes: reference is useful even if the Cc: stable isn't
relevant.
This fixes the issue I reported -- where I needed to revert commit
a0b69cc8e5 ("nvmet-fc: cleanup nvmet add_port/remove_port") to allow
nvme connect to work with fcloop.
Christoph, please feel free to add:
Fixes: a0b69cc8e5 ("nvmet-fc: cleanup nvmet add_port/remove_port")
Tested-by: Mike Snitzer <snitzer at redhat.com>
next prev parent reply other threads:[~2017-12-22 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 16:43 [PATCH] nvmet_fc: correct broken add_port James Smart
2017-12-22 7:23 ` Johannes Thumshirn
2017-12-22 15:50 ` James Smart
2017-12-22 16:41 ` Mike Snitzer [this message]
2017-12-29 9:41 ` Christoph Hellwig
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=20171222164113.GA31385@redhat.com \
--to=snitzer@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.