From: Christoph Hellwig <hch@lst.de>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>
Subject: Re: [PATCH] nvmet: use try_cmpxchg in nvmet_update_sq_head
Date: Tue, 1 Nov 2022 10:45:29 +0100 [thread overview]
Message-ID: <20221101094529.GB12858@lst.de> (raw)
In-Reply-To: <20221020153540.8226-1-ubizjak@gmail.com>
Thanks,
applied to nvme-6.2.
prev parent reply other threads:[~2022-11-01 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 15:35 [PATCH] nvmet: use try_cmpxchg in nvmet_update_sq_head Uros Bizjak
2022-10-23 8:22 ` Sagi Grimberg
2022-10-25 0:47 ` Chaitanya Kulkarni
2022-10-25 6:48 ` Uros Bizjak
2022-11-01 9:45 ` 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=20221101094529.GB12858@lst.de \
--to=hch@lst.de \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=ubizjak@gmail.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