From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Keith Busch <kbusch@kernel.org>
Cc: linux-nvme@lists.infradead.org, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@infradead.org>,
Sagi Grimberg <sagi@grimberg.me>,
Nilay Shroff <nilay@linux.ibm.com>
Subject: Re: [PATCH 0/2] nvme-tcp: lockdep: use dynamic lockdep keys per socket instance
Date: Wed, 3 Jun 2026 20:01:43 +0900 [thread overview]
Message-ID: <aiAJV2Hi05Wt4961@shinmob> (raw)
In-Reply-To: <ah_3h7cIS8e6QTdT@kbusch-mbp>
On Jun 03, 2026 / 10:44, Keith Busch wrote:
...
> > Shin'ichiro Kawasaki (2):
> > nvme-tcp: move nvme_tcp_reclassify_socket()
> > nvme-tcp: lockdep: use dynamic lockdep keys per socket instance
>
> Thanks, patch 1 is applied. Please have a look at my comment on patch 2
> and let me know if we need to respin that version for it.
Thanks! I will post v2 of the patch 2.
prev parent reply other threads:[~2026-06-03 11:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-30 5:20 [PATCH 0/2] nvme-tcp: lockdep: use dynamic lockdep keys per socket instance Shin'ichiro Kawasaki
2026-05-30 5:20 ` [PATCH 1/2] nvme-tcp: move nvme_tcp_reclassify_socket() Shin'ichiro Kawasaki
2026-05-31 15:21 ` Nilay Shroff
2026-06-01 7:06 ` Christoph Hellwig
2026-05-30 5:20 ` [PATCH 2/2] nvme-tcp: lockdep: use dynamic lockdep keys per socket instance Shin'ichiro Kawasaki
2026-05-31 15:22 ` Nilay Shroff
2026-06-01 7:06 ` Christoph Hellwig
2026-06-02 10:13 ` Keith Busch
2026-06-03 11:00 ` Shin'ichiro Kawasaki
2026-06-03 9:44 ` [PATCH 0/2] " Keith Busch
2026-06-03 11:01 ` Shin'ichiro Kawasaki [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=aiAJV2Hi05Wt4961@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nilay@linux.ibm.com \
--cc=sagi@grimberg.me \
/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