From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>
Cc: "Maciej S . Szmigiero" <mail@maciej.szmigiero.name>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH v4 0/7]
Date: Mon, 31 Oct 2022 01:59:39 +0000 [thread overview]
Message-ID: <dd214de3-2501-e0d0-824e-a3b893dd012c@nvidia.com> (raw)
In-Reply-To: <20221031015329.141954-1-damien.lemoal@opensource.wdc.com>
On 10/30/2022 6:53 PM, Damien Le Moal wrote:
> These patches cleanup and improve libata support for the FUA device
> feature. Patch 6 enables FUA support by default for any drive that
> reports supporting the feature as well as NCQ.
>
>
subject line would be really useful to check the previous
discussions ...
-ck
next prev parent reply other threads:[~2022-10-31 1:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 1:53 [PATCH v4 0/7] Damien Le Moal
2022-10-31 1:53 ` [PATCH v4 1/7] block: Prevent the use of REQ_FUA with read operations Damien Le Moal
2022-10-31 1:53 ` [PATCH v4 2/7] ata: libata: Introduce ata_ncq_supported() Damien Le Moal
2022-10-31 1:53 ` [PATCH v4 3/7] ata: libata: Rename and cleanup ata_rwcmd_protocol() Damien Le Moal
2022-10-31 1:53 ` [PATCH v4 4/7] ata: libata: cleanup fua support detection Damien Le Moal
2022-10-31 1:53 ` [PATCH v4 5/7] ata: libata: Fix FUA handling in ata_build_rw_tf() Damien Le Moal
2022-11-02 14:25 ` Hannes Reinecke
2022-10-31 1:53 ` [PATCH v4 6/7] ata: libata: blacklist FUA support for known buggy drives Damien Le Moal
2022-10-31 1:53 ` [PATCH v4 7/7] ata: libata: Enable fua support by default Damien Le Moal
2022-10-31 1:59 ` Chaitanya Kulkarni [this message]
2022-10-31 2:19 ` [PATCH v4 0/7] 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=dd214de3-2501-e0d0-824e-a3b893dd012c@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@opensource.wdc.com \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=mail@maciej.szmigiero.name \
/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