From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: linux-ide@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Cc: Sergey Shtylyov <s.shtylyov@omp.ru>
Subject: [PATCH v2 0/5] libata.force improvements
Date: Mon, 25 Apr 2022 10:34:12 +0900 [thread overview]
Message-ID: <20220425013417.3947791-1-damien.lemoal@opensource.wdc.com> (raw)
This patch series improves the usefulness of the libata.force kernel
boot parameters to facilitate field debugging of ata drives and adapter
issues by extending the range of horkage flags and link flags that can
be controlled.
The first patch is a simple cleanup of the drive blacklist array.
Patch 2 refactors the declaration of the force_tbl array defining the
possible values that libata.force can take. Patch 3 and 4 extend this
array adding most horkage flags and one link flag. Finally, patch 5
updates the kernel documentation reflecting these changes.
Changes from v1:
* Changed force_lflag_on() macro name to force_lflag() in patch 2.
Patch 3 introduce the on & onoff naming of the macro.
* Updated the commit message of patch 2 and 3.
* Removed underscores in the onoff horkage option names in patch 4.
* Added review tags.
Damien Le Moal (5):
ata: libata-core: cleanup ata_device_blacklist
ata: libata-core: Refactor force_tbl definition
ata: libata-core: Improve link flags forced settings
ata: libata-core: Allow forcing most horkage flags
doc: admin-guide: Update libata kernel parameters
.../admin-guide/kernel-parameters.txt | 71 +++--
drivers/ata/libata-core.c | 271 +++++++++++-------
2 files changed, 217 insertions(+), 125 deletions(-)
--
2.35.1
next reply other threads:[~2022-04-25 1:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 1:34 Damien Le Moal [this message]
2022-04-25 1:34 ` [PATCH v2 1/5] ata: libata-core: cleanup ata_device_blacklist Damien Le Moal
2022-04-25 5:49 ` Hannes Reinecke
2022-04-25 1:34 ` [PATCH v2 2/5] ata: libata-core: Refactor force_tbl definition Damien Le Moal
2022-04-25 5:51 ` Hannes Reinecke
2022-04-25 1:34 ` [PATCH v2 3/5] ata: libata-core: Improve link flags forced settings Damien Le Moal
2022-04-25 5:56 ` Hannes Reinecke
2022-04-25 6:08 ` Damien Le Moal
2022-04-25 6:10 ` Hannes Reinecke
2022-04-25 1:34 ` [PATCH v2 4/5] ata: libata-core: Allow forcing most horkage flags Damien Le Moal
2022-04-25 6:00 ` Hannes Reinecke
2022-04-25 6:15 ` Damien Le Moal
2022-04-25 6:44 ` Hannes Reinecke
2022-04-25 1:34 ` [PATCH v2 5/5] doc: admin-guide: Update libata kernel parameters Damien Le Moal
2022-04-25 1:37 ` Damien Le Moal
2022-04-25 6:01 ` Hannes Reinecke
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=20220425013417.3947791-1-damien.lemoal@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=s.shtylyov@omp.ru \
/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