From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Niklas Cassel <cassel@kernel.org>
Cc: Damien Le Moal <dlemoal@kernel.org>,
linux-ide@vger.kernel.org, xxjack12xx@gmail.com
Subject: Re: [PATCH v2 0/8] ata: libata: Quirk DELLBOSS VD max_sectors
Date: Sat, 29 Nov 2025 16:50:32 -0500 [thread overview]
Message-ID: <yq1sedwwltf.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20251128084814.3798425-10-cassel@kernel.org> (Niklas Cassel's message of "Fri, 28 Nov 2025 09:48:15 +0100")
Niklas,
> It seems like a lot for SATA controllers are buggy and don't really
> like this, see: https://bugzilla.kernel.org/show_bug.cgi?id=220693
>
> For now, we only add a DELLBOSS VD max_sectors quirk, but surely we
> will need to quirk additional controllers.
Looks OK to me.
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
--
Martin K. Petersen
prev parent reply other threads:[~2025-11-29 21:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 8:48 [PATCH v2 0/8] ata: libata: Quirk DELLBOSS VD max_sectors Niklas Cassel
2025-11-28 8:48 ` [PATCH v2 1/8] ata: libata: Move quirk flags to their own enum Niklas Cassel
2025-11-28 8:48 ` [PATCH v2 2/8] ata: libata: Add ATA_QUIRK_MAX_SEC and convert all device quirks Niklas Cassel
2025-11-28 8:48 ` [PATCH v2 3/8] ata: libata: Add ata_force_get_fe_for_dev() helper Niklas Cassel
2025-11-28 8:48 ` [PATCH v2 4/8] ata: libata: Change libata.force to use the generic ATA_QUIRK_MAX_SEC quirk Niklas Cassel
2025-11-28 8:48 ` [PATCH v2 5/8] ata: libata-core: Quirk DELLBOSS VD max_sectors Niklas Cassel
2025-11-28 9:00 ` Niklas Cassel
2025-11-28 8:48 ` [PATCH v2 6/8] ata: libata: Add support to parse equal sign in libata.force Niklas Cassel
2025-11-28 8:48 ` [PATCH v2 7/8] ata: libata: Add libata.force parameter max_sec Niklas Cassel
2025-11-28 8:48 ` [PATCH v2 8/8] ata: libata: Allow more quirks Niklas Cassel
2025-11-29 21:50 ` Martin K. Petersen [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=yq1sedwwltf.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=xxjack12xx@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