From: Christoph Hellwig <hch@lst.de>
To: Tao Jiang <tanroame.kyle@gmail.com>
Cc: linux-nvme@lists.infradead.org, kbusch@kernel.org,
axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvme-pci: add quirk for Memblaze Pblaze5 (0x1c5f:0x0555)
Date: Thu, 16 Apr 2026 07:17:03 +0200 [thread overview]
Message-ID: <20260416051703.GA14917@lst.de> (raw)
In-Reply-To: <1776274035-1604-1-git-send-email-tanroame.kyle@gmail.com>
Me, another broken device :( I wonder how these people test their
hardware..
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2026-04-16 5:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 17:27 [PATCH] nvme-pci: add quirk for Memblaze Pblaze5 (0x1c5f:0x0555) Tao Jiang
2026-04-16 5:17 ` Christoph Hellwig [this message]
2026-04-16 22:11 ` Keith Busch
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=20260416051703.GA14917@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=tanroame.kyle@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