public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Wolf <snow.wolf.29@proton.me>, Damien Le Moal <dlemoal@kernel.org>
Cc: "1120831@bugs.debian.org" <1120831@bugs.debian.org>,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH] ata: libata-core: Quirk INTEL SSDSC2KG480G8 max_sectors
Date: Tue, 20 Jan 2026 14:49:14 +0100	[thread overview]
Message-ID: <aW-H2uEwgjKoU7ma@ryzen> (raw)
In-Reply-To: <kH1HPlwkQ_5AcoiqCiLZ7VgrxVC0bJBfB_Bo_1hlMfUwn6ebZHhEtBTAmkzMPBkp50zHeUqMGGzRKmAWp4XheOQjQNRNPPn5JajTY5TZnRk=@proton.me>

Hello Wolf,

On Tue, Jan 20, 2026 at 01:29:27PM +0000, Wolf wrote:
> > Hello Wolf,
> >
> > please test this patch and see if it works.
> >
> > The patch is based on the for-next branch of:
> > git://git.kernel.org/pub/scm/linux/kernel/git/libata/linux.git
> >
> > 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 e888f2445692..8e41e8a33096 100644
> > --- a/drivers/ata/libata-core.c
> > +++ b/drivers/ata/libata-core.c
> > @@ -4082,6 +4082,7 @@ static const struct ata_dev_quirk_value __ata_dev_max_sec_quirks[] = {
> > { "LITEON CX1-JB*-HP", NULL, 1024 },
> > { "LITEON EP1-", NULL, 1024 },
> > { "DELLBOSS VD", "MV.R00-0", 8191 },
> > + { "INTEL SSDSC2KG480G8", "XCV10120", 8191 },
> > { },
> > };
> >
> > @@ -4336,6 +4337,8 @@ static const struct ata_dev_quirks_entry __ata_dev_quirks[] = {
> >
> > { "Micron", NULL, ATA_QUIRK_ZERO_AFTER_TRIM },
> > { "Crucial*", NULL, ATA_QUIRK_ZERO_AFTER_TRIM },
> > + { "INTEL SSDSC2KG480G8", "XCV10120", ATA_QUIRK_ZERO_AFTER_TRIM |
> > + ATA_QUIRK_MAX_SEC },
> > { "INTELSSD", NULL, ATA_QUIRK_ZERO_AFTER_TRIM },
> > { "SSDINTEL", NULL, ATA_QUIRK_ZERO_AFTER_TRIM },
> > { "SamsungSSD", NULL, ATA_QUIRK_ZERO_AFTER_TRIM },
> > --
> > 2.52.0
> 
> Hello Niklas,
> 
> The patched linux/6.19.0~rc1 is working.

Thank you for testing!

Hopefully Damien can queue it up.

I suggest queueing it up for for-next,
since it depends on some patches there.


Kind regards,
Niklas

  parent reply	other threads:[~2026-01-20 13:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20 10:32 [PATCH] ata: libata-core: Quirk INTEL SSDSC2KG480G8 max_sectors Niklas Cassel
     [not found] ` <kH1HPlwkQ_5AcoiqCiLZ7VgrxVC0bJBfB_Bo_1hlMfUwn6ebZHhEtBTAmkzMPBkp50zHeUqMGGzRKmAWp4XheOQjQNRNPPn5JajTY5TZnRk=@proton.me>
2026-01-20 13:49   ` Niklas Cassel [this message]
2026-01-22 15:09 ` Martin K. Petersen
2026-01-26  6:43 ` 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=aW-H2uEwgjKoU7ma@ryzen \
    --to=cassel@kernel.org \
    --cc=1120831@bugs.debian.org \
    --cc=dlemoal@kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=snow.wolf.29@proton.me \
    /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