From: Damien Le Moal <dlemoal@kernel.org>
To: Niklas Cassel <cassel@kernel.org>
Cc: Emerson Pinter <e@pinter.dev>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] ata: libata-core: Disable LPM on ST2000DM008-2FR102
Date: Tue, 9 Dec 2025 20:30:01 -0800 [thread overview]
Message-ID: <66ea31a4-0ae2-4ada-b253-224cc4ae596b@kernel.org> (raw)
In-Reply-To: <aTja9mQwpjAJqrFd@dhcp-10-89-81-223>
On 2025/12/09 18:29, Niklas Cassel wrote:
> On Tue, Dec 09, 2025 at 05:42:37PM -0800, Damien Le Moal wrote:
>> On 2025/12/08 20:24, Niklas Cassel wrote:
>>> According to a user report, the ST2000DM008-2FR102 has problems with LPM.
>>>
>>> Reported-by: Emerson Pinter <e@pinter.dev>
>>> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=220693
>>> Signed-off-by: Niklas Cassel <cassel@kernel.org>
>>> ---
>>> drivers/ata/libata-core.c | 3 +++
>>> 1 file changed, 3 insertions(+)
>>>
>>> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
>>> index b96105481784..94c0e0ff981f 100644
>>> --- a/drivers/ata/libata-core.c
>>> +++ b/drivers/ata/libata-core.c
>>> @@ -4187,6 +4187,9 @@ static const struct ata_dev_quirks_entry __ata_dev_quirks[] = {
>>> ATA_QUIRK_NOLPM },
>>> { "VB0250EAVER", "HPG7", ATA_QUIRK_BROKEN_FPDMA_AA },
>>>
>>> + /* ST disks with LPM issues */
>>
>> s/ST/Seagate
>>
>> Other than that, looks good.
>
> Perhaps you can fix up while applying?
OK. Will do.
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2025-12-10 4:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 4:24 [PATCH] ata: libata-core: Disable LPM on ST2000DM008-2FR102 Niklas Cassel
2025-12-09 4:25 ` Niklas Cassel
2025-12-10 1:42 ` Damien Le Moal
2025-12-10 2:29 ` Niklas Cassel
2025-12-10 4:30 ` Damien Le Moal [this message]
2025-12-16 5:30 ` Damien Le Moal
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=66ea31a4-0ae2-4ada-b253-224cc4ae596b@kernel.org \
--to=dlemoal@kernel.org \
--cc=cassel@kernel.org \
--cc=e@pinter.dev \
--cc=linux-ide@vger.kernel.org \
/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