From: Damien Le Moal <dlemoal@kernel.org>
To: Hannes Reinecke <hare@suse.de>,
Phil Pemberton <philpem@philpem.me.uk>,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Niklas Cassel <cassel@kernel.org>,
"James E . J . Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH v3 7/7] scsi: scsi_devinfo: extend BLIST_NO_LUN_1F to MATSHITA and NEC PD-1 variants
Date: Tue, 12 May 2026 06:54:11 +0900 [thread overview]
Message-ID: <1436af33-87d8-4070-ae67-a6a290fc0240@kernel.org> (raw)
In-Reply-To: <ea4de81e-4c9b-48d0-bc6d-72f23c7fc831@suse.de>
On 5/8/26 15:02, Hannes Reinecke wrote:
>> Only that these are optional to the feature work and untested as I don't
>> have hardware. I believe these drives use the same PD-1 mechanism and
>> firmware so should behave the same, but I can't prove it.
>>
>> The intent was to allow the 1-6 set to be merged (as these are tested)
>> without 7/7 (which is not) to minimise the risk of regressions.
>>
> So drop it, then.
> We can always add it later once someone shows up who actually has the
> hardware.
I agreee, let's drop this one and patch only once it can be confirmed that the
change is needed.
--
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2026-05-11 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260426190920.2051289-1-philpem@philpem.me.uk>
[not found] ` <20260426190920.2051289-8-philpem@philpem.me.uk>
[not found] ` <c1db6016-9b7d-454b-a4a8-c8f61391c5ae@suse.de>
2026-05-06 0:52 ` [PATCH v3 7/7] scsi: scsi_devinfo: extend BLIST_NO_LUN_1F to MATSHITA and NEC PD-1 variants Phil Pemberton
2026-05-08 6:02 ` Hannes Reinecke
2026-05-11 21:54 ` Damien Le Moal [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=1436af33-87d8-4070-ae67-a6a290fc0240@kernel.org \
--to=dlemoal@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=cassel@kernel.org \
--cc=hare@suse.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=philpem@philpem.me.uk \
/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