From: Keith Busch <kbusch@kernel.org>
To: Hannes Reinecke <hare@suse.de>
Cc: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvmet-tcp: use 'spin_lock_bh' for state_lock()
Date: Fri, 13 Oct 2023 08:35:04 -0600 [thread overview]
Message-ID: <ZSlVmG3ju2xnZwt8@kbusch-mbp> (raw)
In-Reply-To: <787c2581-d9b0-404e-ac2d-764324af3fc9@suse.de>
Applied to nvme-6.7, thanks!
next prev parent reply other threads:[~2023-10-13 14:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 12:59 [PATCH] nvmet-tcp: use 'spin_lock_bh' for state_lock() Hannes Reinecke
2023-10-12 15:09 ` Keith Busch
2023-10-12 16:18 ` Hannes Reinecke
2023-10-13 14:35 ` Keith Busch [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-10 13:19 Hannes Reinecke
2023-08-13 12:52 ` Sagi Grimberg
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=ZSlVmG3ju2xnZwt8@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=linux-nvme@lists.infradead.org \
--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