From: Keith Busch <kbusch@kernel.org>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: shlomin@mellanox.com, Max Gurtovoy <maxg@mellanox.com>,
hch@lst.de, linux-nvme@lists.infradead.org, israelr@mellanox.com
Subject: Re: [PATCH 1/1] nvme-rdma: fix a segmentation fault during module unload
Date: Wed, 30 Oct 2019 11:20:57 +0900 [thread overview]
Message-ID: <20191030022057.GD15332@redsun51.ssa.fujisawa.hgst.com> (raw)
In-Reply-To: <20191030004643.GB15332@redsun51.ssa.fujisawa.hgst.com>
On Wed, Oct 30, 2019 at 09:46:43AM +0900, Keith Busch wrote:
> Thanks, applied to nvme-5.5.
Oops, this one is a fixes, so I've put this patch in 5.4, and the other
in 5.5.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2019-10-30 2:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 14:42 [PATCH 1/1] nvme-rdma: fix a segmentation fault during module unload Max Gurtovoy
2019-10-29 17:14 ` Sagi Grimberg
2019-10-30 0:46 ` Keith Busch
2019-10-30 2:20 ` Keith Busch [this message]
2019-10-30 8:44 ` Max Gurtovoy
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=20191030022057.GD15332@redsun51.ssa.fujisawa.hgst.com \
--to=kbusch@kernel.org \
--cc=hch@lst.de \
--cc=israelr@mellanox.com \
--cc=linux-nvme@lists.infradead.org \
--cc=maxg@mellanox.com \
--cc=sagi@grimberg.me \
--cc=shlomin@mellanox.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;
as well as URLs for NNTP newsgroup(s).