From: Christoph Hellwig <hch@lst.de>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvme: add device name to warning in uuid_show()
Date: Mon, 13 Jun 2022 19:58:03 +0200 [thread overview]
Message-ID: <20220613175803.GC15847@lst.de> (raw)
In-Reply-To: <20220607155555.8623-1-linux@weissschuh.net>
Thanks,
applied to nvme-5.19 with the small whitespace fixup.
prev parent reply other threads:[~2022-06-13 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 15:55 [PATCH] nvme: add device name to warning in uuid_show() Thomas Weißschuh
2022-06-07 16:11 ` Keith Busch
2022-06-07 22:55 ` Thomas Weißschuh
2022-06-13 17:58 ` 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=20220613175803.GC15847@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux@weissschuh.net \
--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