public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-ide@vger.kernel.org
Cc: Damien Le Moal <dlemoal@kernel.org>, Niklas Cassel <cassel@kernel.org>
Subject: [GIT PULL] ata fixes for 7.0-rc5
Date: Fri, 20 Mar 2026 10:55:38 +0100	[thread overview]
Message-ID: <20260320095538.133163-1-cassel@kernel.org> (raw)

Linus,

The following changes since commit ee0e6e69a772d601e152e5368a1da25d656122a8:

  ata: libata-eh: Fix detection of deferred qc timeouts (2026-03-06 09:58:47 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/libata/linux tags/ata-7.0-rc5

for you to fetch changes up to e6d7eba23b666d85cacee0643be280d6ce1ebffc:

  ata: libata-scsi: report correct sense field pointer in ata_scsiop_maint_in() (2026-03-20 09:59:30 +0100)

----------------------------------------------------------------
ata fixes for 7.0-rc5

 - ADATA SU680 SSDs are causing command timeouts when LPM is enabled.
   Enable the ATA_QUIRK_NOLPM quirk to prevent LPM from being enabled
   on these devices. (Damien)

 - When receiving a REPORT SUPPORTED OPERATION CODES command with an
   invalid REPORTING OPTIONS format, sense data should have the field
   pointer set to byte 2 (the location of the REPORTING OPTIONS field)
   instead of incorrectly pointing to byte 1. (Damien)

----------------------------------------------------------------
Damien Le Moal (2):
      ata: libata-core: disable LPM on ADATA SU680 SSD
      ata: libata-scsi: report correct sense field pointer in ata_scsiop_maint_in()

 drivers/ata/libata-core.c | 3 +++
 drivers/ata/libata-scsi.c | 2 +-
 2 files changed, 4 insertions(+), 1 deletion(-)

             reply	other threads:[~2026-03-20  9:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20  9:55 Niklas Cassel [this message]
2026-03-20 17:13 ` [GIT PULL] ata fixes for 7.0-rc5 pr-tracker-bot

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=20260320095538.133163-1-cassel@kernel.org \
    --to=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=torvalds@linux-foundation.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