From: Christoph Hellwig <hch@lst.de>
To: Daniel Wagner <wagi@kernel.org>
Cc: James Smart <james.smart@broadcom.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>, Jens Axboe <axboe@kernel.dk>,
Hannes Reinecke <hare@suse.de>,
James Smart <jsmart2021@gmail.com>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] nvmet-fcloop: bunch of fixes and cleanups
Date: Wed, 9 Apr 2025 13:05:47 +0200 [thread overview]
Message-ID: <20250409110547.GA6059@lst.de> (raw)
In-Reply-To: <20250408-nvmet-fcloop-part-one-v1-0-382ec97ab7eb@kernel.org>
Thanks,
I've added the entire series to the nvme-6.15 branch.
prev parent reply other threads:[~2025-04-09 11:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 15:29 [PATCH 0/8] nvmet-fcloop: bunch of fixes and cleanups Daniel Wagner
2025-04-08 15:29 ` [PATCH 1/8] nvmet-fcloop: swap list_add_tail arguments Daniel Wagner
2025-04-09 6:09 ` Hannes Reinecke
2025-04-09 10:58 ` Christoph Hellwig
2025-04-08 15:29 ` [PATCH 2/8] nvmet-fcloop: replace kref with refcount Daniel Wagner
2025-04-08 15:29 ` [PATCH 3/8] nvmet-fcloop: add ref counting to lport Daniel Wagner
2025-04-08 15:29 ` [PATCH 4/8] nvmet-fc: inline nvmet_fc_delete_assoc Daniel Wagner
2025-04-08 15:29 ` [PATCH 5/8] nvmet-fc: inline nvmet_fc_free_hostport Daniel Wagner
2025-04-08 15:29 ` [PATCH 6/8] nvmet-fc: update tgtport ref per assoc Daniel Wagner
2025-04-08 15:29 ` [PATCH 7/8] nvmet-fc: take tgtport reference only once Daniel Wagner
2025-04-08 15:29 ` [PATCH 8/8] nvmet-fc: put ref when assoc->del_work is already scheduled Daniel Wagner
2025-04-09 11:05 ` Christoph Hellwig [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=20250409110547.GA6059@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=james.smart@broadcom.com \
--cc=jsmart2021@gmail.com \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=wagi@kernel.org \
/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.