From: Niklas Cassel <cassel@kernel.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: linux-ide@vger.kernel.org, grandmastertriplej@gmail.com,
Mario Limonciello <mario.limonciello@amd.com>,
"Natikar, Basavaraj" <basavaraj.natikar@amd.com>,
Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
Subject: Re: [PATCH 2/2] ata: libata: Correct libata.force parameter documentation
Date: Mon, 21 Sep 2026 13:26:36 +0200 [thread overview]
Message-ID: <arEUbNHVitKZWACC@ryzen> (raw)
In-Reply-To: <1022afd9-3443-4f1d-a35a-e550615a67d6@kernel.org>
On Sun, Sep 20, 2026 at 01:35:40PM +0900, Damien Le Moal wrote:
> >
> > Hmm.. I guess we could theoretically remove the [no]ncqati parameter from
> > libata.force.
> > If a user wants to enable/disable ncq, they can use the [no]ncq libata.force
> > parameter.
> >
> > However, since this libata.force kernel parameter already exists, I guess it
> > might actually be used by someone, so we can't really remove it without
> > potentially breaking existing setups, so I guess the easiest thing is just
> > to keep it, even if it is not strictly needed.
>
> It can be needed on a machine that has multiple adapters from different vendors.
libata.force parameters can be applied per port, so even for machines with
multiple adapters, it would have been sufficient IMO.
Kind regards,
Niklas
next prev parent reply other threads:[~2026-09-21 11:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 12:40 [PATCH 0/2] ata: Extend Samsung LPM quirk to AMD and fix force documentation Niklas Cassel
2026-09-18 12:40 ` [PATCH 1/2] ata: libata-core: Extend Samsung LPM quirk to AMD controllers Niklas Cassel
2026-09-19 17:21 ` Mario Limonciello
2026-09-20 4:33 ` Damien Le Moal
2026-09-18 12:40 ` [PATCH 2/2] ata: libata: Correct libata.force parameter documentation Niklas Cassel
2026-09-18 12:49 ` Niklas Cassel
2026-09-20 4:35 ` Damien Le Moal
2026-09-21 11:26 ` Niklas Cassel [this message]
2026-09-20 4:34 ` Damien Le Moal
2026-09-21 11:21 ` [PATCH 0/2] ata: Extend Samsung LPM quirk to AMD and fix force documentation 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=arEUbNHVitKZWACC@ryzen \
--to=cassel@kernel.org \
--cc=Shyam-sundar.S-k@amd.com \
--cc=basavaraj.natikar@amd.com \
--cc=dlemoal@kernel.org \
--cc=grandmastertriplej@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=mario.limonciello@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.