Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Tommy Kelly <linux@tkel.ly>, Niklas Cassel <cassel@kernel.org>
Cc: linux-ide@vger.kernel.org,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	John Garry <john.g.garry@oracle.com>
Subject: Re: [PATCH v3 2/2] ata: libata-scsi: do not needlessly defer commands when using PMP with FBS
Date: Tue, 12 May 2026 16:42:28 +0900	[thread overview]
Message-ID: <20ed30b4-66a1-4ca6-aa1a-98960273797f@kernel.org> (raw)
In-Reply-To: <38ec669a-f69c-4c55-9f47-995d6722806f@tkel.ly>

On 5/12/26 11:41, Tommy Kelly wrote:
> On 5/11/26 19:01, Damien Le Moal wrote:
>> Looks OK. However Tommy did see a warning, so I wonder if we still have
>> something missing...
> Sorry if I'm causing confusion, for clarity:
> I didn't see the warning with this v3 patchset applied.
> I saw a warning with vanilla linux 6.19.12.
> I just recently got FBS working so I was reporting any issues with old code + FBS for completeness.
> 
> With this v3 patchset + FBS, no issues or warnings.

Thank you for clarifying. It would be interesting to test this v3 but without
the FBS support. Could you try please ?

> 
> Best,
> Tommy


-- 
Damien Le Moal
Western Digital Research

  reply	other threads:[~2026-05-12  7:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-08 19:50 [PATCH v3 0/2] ata: fix deferred QC handling for port multipliers Niklas Cassel
2026-05-08 19:50 ` [PATCH v3 1/2] ata: libata-scsi: do not use the deferred QC feature on PMPs with CBS Niklas Cassel
2026-05-08 19:50 ` [PATCH v3 2/2] ata: libata-scsi: do not needlessly defer commands when using PMP with FBS Niklas Cassel
2026-05-12  2:01   ` Damien Le Moal
2026-05-12  2:41     ` Tommy Kelly
2026-05-12  7:42       ` Damien Le Moal [this message]
2026-05-12  0:25 ` [PATCH v3 0/2] ata: fix deferred QC handling for port multipliers Tommy Kelly
2026-05-12  1:58 ` Damien Le Moal
2026-05-12 10:37   ` Niklas Cassel

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=20ed30b4-66a1-4ca6-aa1a-98960273797f@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=cassel@kernel.org \
    --cc=john.g.garry@oracle.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux@tkel.ly \
    --cc=martin.petersen@oracle.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