Linux ATA/IDE development
 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.3-rc7
Date: Tue,  6 Oct 2026 12:45:16 +0200	[thread overview]
Message-ID: <20261006104516.2347588-1-cassel@kernel.org> (raw)

Linus,

The following changes since commit 113dcdfadf30ea11fbbdfcd4f6ea87687655cc5b:

  MAINTAINERS: name the libata/linux for-next branch (2026-09-25 11:08:37 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/libata/linux tags/ata-7.3-rc7

for you to fetch changes up to bc8ce2cea5f77c4bd1a5184705e300e83546c0c4:

  ata: libata-scsi: do not lose CHECK CONDITION for failed ATAPI commands (2026-09-30 10:42:26 +0200)

----------------------------------------------------------------
ata fix for 7.3-rc7

 - Set CHECK CONDITION for failed ATAPI commands.

   Since commit 2e1d2e65e773 ("ata: libata-scsi: terminate deferred
   commands on time out") failed ATAPI commands incorrectly stopped
   having CHECK CONDITION set for commands that had a SCSI midlayer
   byte set by scsi_check_sense(). SG_IO users therefore saw failed
   ATAPI commands as successful. (Hengyu)

----------------------------------------------------------------
Hengyu Liang (1):
      ata: libata-scsi: do not lose CHECK CONDITION for failed ATAPI commands

 drivers/ata/libata-scsi.c | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

             reply	other threads:[~2026-10-06 10:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-06 10:45 Niklas Cassel [this message]
2026-10-06 14:14 ` [GIT PULL] ata fixes for 7.3-rc7 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=20261006104516.2347588-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