From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
<linux-ide@vger.kernel.org>,
"Maciej S . Szmigiero" <mail@maciej.szmigiero.name>
Cc: Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH v2 3/3] ata: libata: Enable fua support by default
Date: Mon, 24 Oct 2022 13:16:50 +0300 [thread overview]
Message-ID: <52f3c988-3432-64d6-e38f-603b881c31ce@omp.ru> (raw)
In-Reply-To: <20221024072609.346502-4-damien.lemoal@opensource.wdc.com>
Hello!
On 10/24/22 10:26 AM, Damien Le Moal wrote:
> Change the default value of the fua module parameter to 1 to enable fua
> support by default for all devices supporting it. This parameter
> description is also updated to indicate it is deprecated and that
> libata.force=[no]fua should be used to control fua support.
Mhm, where is that change? You only seem to change the default...
>
> Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
> Reviewed-by: Hannes Reinecke <hare@suse.de>
> ---
> drivers/ata/libata-core.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
> index 27aec8e63a8c..867e2c423627 100644
> --- a/drivers/ata/libata-core.c
> +++ b/drivers/ata/libata-core.c
> @@ -127,9 +127,9 @@ int atapi_passthru16 = 1;
> module_param(atapi_passthru16, int, 0444);
> MODULE_PARM_DESC(atapi_passthru16, "Enable ATA_16 passthru for ATAPI devices (0=off, 1=on [default])");
>
> -int libata_fua = 0;
> +int libata_fua = 1;
> module_param_named(fua, libata_fua, int, 0444);
> -MODULE_PARM_DESC(fua, "FUA support (0=off [default], 1=on)");
> +MODULE_PARM_DESC(fua, "FUA support (0=off, 1=on [default])");
>
> static int ata_ignore_hpa;
> module_param_named(ignore_hpa, ata_ignore_hpa, int, 0644);
MBR, Sergey
next prev parent reply other threads:[~2022-10-24 10:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 7:26 [PATCH v2 0/3] Improve libata support for FUA Damien Le Moal
2022-10-24 7:26 ` [PATCH v2 1/3] ata: libata: cleanup fua handling Damien Le Moal
2022-10-24 7:26 ` [PATCH v2 2/3] ata: libata: blacklist FUA support for known buggy drives Damien Le Moal
2022-10-24 7:52 ` Hannes Reinecke
2022-10-24 7:26 ` [PATCH v2 3/3] ata: libata: Enable fua support by default Damien Le Moal
2022-10-24 10:16 ` Sergey Shtylyov [this message]
2022-10-24 11:15 ` Damien Le Moal
2022-10-24 18:48 ` [PATCH v2 0/3] Improve libata support for FUA Maciej S. Szmigiero
2022-10-24 22:09 ` Damien Le Moal
2022-10-24 23:26 ` Damien Le Moal
2022-10-25 0:22 ` Damien Le Moal
2022-10-25 7:05 ` Hannes Reinecke
2022-10-25 8:59 ` Damien Le Moal
2022-10-25 9:41 ` Niklas Cassel
2022-10-25 18:13 ` Maciej S. Szmigiero
2022-10-25 23:21 ` Damien Le Moal
2022-10-25 9:01 ` 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=52f3c988-3432-64d6-e38f-603b881c31ce@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=damien.lemoal@opensource.wdc.com \
--cc=hare@suse.de \
--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