From: Christoph Hellwig <hch@lst.de>
To: Judy Brock <judy.brock@samsung.com>
Cc: "Ballard, Curtis C (HPE Storage)" <curtis.ballard@hpe.com>,
Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>,
"hare@kernel.org" <hare@kernel.org>,
Keith Busch <kbusch@kernel.org>, Sagi Grimberg <sagi@grimberg.me>,
"wagi@lst.de" <wagi@lst.de>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Javier Gonzalez <javier.gonz@samsung.com>
Subject: Re: [PATCH 0/2] nvme: handle partially unique NID value
Date: Fri, 2 May 2025 12:25:05 +0200 [thread overview]
Message-ID: <20250502102505.GA13055@lst.de> (raw)
In-Reply-To: <eee8de0a44074dd3bfb0fc6ec425b647@samsung.com>
Judy, stop it. HP could have trivially asked Samsung for a firmware
update and gotten it in the time they used all their commercial channels
to fight actually having to fix their intentional stupidity.
If you are a supposedly legit enterprise storage vendor and ask your SSD
vendor for a non-standard data corrupting feature you have to admit your
failure and fix it. And I'm amazed how HP is trying to flex their
commercial muscle to get around not having to admit their failure and
fix it, and I'm also really surprised how little spine you folks have to
play along with this.
This is very disappointing and does not make you a trustworthy actor.
next prev parent reply other threads:[~2025-05-02 10:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250414090959.2015-1-hare@kernel.org>
2025-04-14 11:19 ` [PATCH 0/2] nvme: handle partially unique NID value Christoph Hellwig
2025-04-14 11:31 ` Hannes Reinecke
2025-04-14 11:41 ` Christoph Hellwig
2025-04-14 11:55 ` Hannes Reinecke
2025-04-14 11:59 ` Christoph Hellwig
2025-04-17 16:56 ` Ballard, Curtis C (HPE Storage)
[not found] ` <CGME20250502082359uscas1p1e2a9858dcc9200ab1d1d863c4495fc0a@uscas1p1.samsung.com>
[not found] ` <eee8de0a44074dd3bfb0fc6ec425b647@samsung.com>
2025-05-02 10:25 ` Christoph Hellwig [this message]
[not found] ` <27a99b458f0144fba094726e4f470552@samsung.com>
2025-05-03 3:46 ` Keith Busch
2025-05-05 9:51 ` Javier Gonzalez
2025-05-05 11:11 ` Christoph Hellwig
2025-05-05 13:08 ` Javier Gonzalez
2025-05-05 13:49 ` Laurence Oberman
2025-05-06 7:07 ` Javier Gonzalez
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=20250502102505.GA13055@lst.de \
--to=hch@lst.de \
--cc=curtis.ballard@hpe.com \
--cc=hare@kernel.org \
--cc=hare@suse.de \
--cc=javier.gonz@samsung.com \
--cc=judy.brock@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=wagi@lst.de \
/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