From: Christoph Hellwig <hch@lst.de>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Mark O'Donovan <shiftee@posteo.net>,
linux-nvme@lists.infradead.org, kernel-janitors@vger.kernel.org,
Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>,
Jens Axboe <axboe@kernel.dk>, Keith Busch <kbusch@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] nvme-auth: unlock mutex in one place only
Date: Mon, 31 Jul 2023 15:51:52 +0200 [thread overview]
Message-ID: <20230731135152.GA6016@lst.de> (raw)
In-Reply-To: <28d11fc5-743f-0810-8ab7-3fa2a3f98c65@web.de>
On Mon, Jul 31, 2023 at 02:00:37PM +0200, Markus Elfring wrote:
> Are imperative change descriptions still preferred?
It doesn't fucking matter. Please stop spamming nvme contributors.
next prev parent reply other threads:[~2023-07-31 13:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 13:47 [PATCH 1/2] nvme-auth: unlock mutex in one place only Mark O'Donovan
2023-07-27 13:47 ` [PATCH 2/2] nvme-auth: set explanation code for failure2 msgs Mark O'Donovan
2023-07-31 5:58 ` Christoph Hellwig
2023-07-31 16:17 ` Hannes Reinecke
2023-07-31 5:55 ` [PATCH 1/2] nvme-auth: unlock mutex in one place only Christoph Hellwig
2023-07-31 12:00 ` Markus Elfring
2023-07-31 13:51 ` Christoph Hellwig [this message]
2023-07-31 17:46 ` [1/2] " Markus Elfring
2023-07-31 18:18 ` Keith Busch
2023-07-31 18:37 ` Markus Elfring
2023-07-31 18:43 ` Keith Busch
2023-07-31 13:51 ` [PATCH 1/2] " 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=20230731135152.GA6016@lst.de \
--to=hch@lst.de \
--cc=Markus.Elfring@web.de \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=kbusch@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=shiftee@posteo.net \
/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