From: Damien Le Moal <dlemoal@kernel.org>
To: linux-ide@vger.kernel.org, Niklas Cassel <cassel@kernel.org>
Subject: [PATCH v4 0/3] Some renaming and horkage improvements
Date: Tue, 23 Jul 2024 19:34:03 +0900 [thread overview]
Message-ID: <20240723103406.294462-1-dlemoal@kernel.org> (raw)
The first 2 patches removes the use of the term "blacklist" from
libata-core.
The third patch adds printing on device scan of the horkage flags that
will be applied to the device to help with debugging.
Changes from v3:
- Corrected the BUILD_BUG_ON() call in patch 3
- Corrected alignment of horkage definition comments in patch 3
Changes from v2:
- Simplified ata_dev_print_horkage() to always print the device
revision (patch 3)
- Simplified ata_dev_horkage() to having 2 different calls to
ata_dev_print_horkage() and to always print the device revision
(patch 3)
- Added a BUILD_BUG_ON() check in patch 3 to ensure that the horkage
flags all fit within an unsigned int.
Changes from v1:
- Remove unused macro definition in patch 3
- Use unsigned int for horkage flags (patch 3)
Damien Le Moal (3):
ata: libata: Rename ata_dma_blacklisted()
ata: libata: Rename ata_dev_blacklisted()
ata: libata: Print horkages applied to devices
drivers/ata/libata-core.c | 112 ++++++++++++++++++++++++++++++--------
include/linux/libata.h | 112 +++++++++++++++++++++++++-------------
2 files changed, 164 insertions(+), 60 deletions(-)
--
2.45.2
next reply other threads:[~2024-07-23 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 10:34 Damien Le Moal [this message]
2024-07-23 10:34 ` [PATCH v4 1/3] ata: libata: Rename ata_dma_blacklisted() Damien Le Moal
2024-07-23 13:34 ` John Garry
2024-07-23 19:28 ` Igor Pylypiv
2024-07-23 10:34 ` [PATCH v4 2/3] ata: libata: Rename ata_dev_blacklisted() Damien Le Moal
2024-07-23 19:29 ` Igor Pylypiv
2024-07-23 10:34 ` [PATCH v4 3/3] ata: libata: Print horkages applied to devices Damien Le Moal
2024-07-23 19:41 ` Igor Pylypiv
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=20240723103406.294462-1-dlemoal@kernel.org \
--to=dlemoal@kernel.org \
--cc=cassel@kernel.org \
--cc=linux-ide@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).