From: Bjorn Helgaas <helgaas@kernel.org>
To: Liu Song <liusong@linux.alibaba.com>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, Andy Whitcroft <apw@canonical.com>,
Joe Perches <joe@perches.com>
Subject: Re: [PATCH] PCI: eliminate abnormal characters when reads help information of "PCI_P2PDMA" under menuconfig
Date: Wed, 20 Jul 2022 12:23:28 -0500 [thread overview]
Message-ID: <20220720172328.GA1647083@bhelgaas> (raw)
In-Reply-To: <1658301723-111283-1-git-send-email-liusong@linux.alibaba.com>
[+cc Andy, Joe, possible checkpatch question]
On Wed, Jul 20, 2022 at 03:22:03PM +0800, Liu Song wrote:
> From: Liu Song <liusong@linux.alibaba.com>
>
> Read the help information of PCI_P2PDMA through make menuconfig,
> "Enables" is partially displayed as garbled characters, so fix it.
>
> Signed-off-by: Liu Song <liusong@linux.alibaba.com>
> ---
> drivers/pci/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/pci/Kconfig b/drivers/pci/Kconfig
> index 133c732..8102b78 100644
> --- a/drivers/pci/Kconfig
> +++ b/drivers/pci/Kconfig
> @@ -166,7 +166,7 @@ config PCI_P2PDMA
> depends on ZONE_DEVICE
> select GENERIC_ALLOCATOR
> help
> - Enableѕ drivers to do PCI peer-to-peer transactions to and from
> + Enables drivers to do PCI peer-to-peer transactions to and from
I see this problem ("Enables" renders as "Enable ~U" because the "s"
is actually UTF-8 D195, CYRILLIC SMALL LETTER DZE).
"file" found the following other Kconfig files that also contain
UTF-8:
drivers/pci/Kconfig
D195 CYRILLIC SMALL LETTER DZE, which looks like "s"
"Enables" renders as "Enable ~U"
net/netfilter/ipvs/Kconfig
C2A0 NO-BREAK SPACE
renders fine
drivers/mtd/nand/raw/Kconfig
MTD_NAND_CAFE C389 LATIN CAPITAL LETTER E WITH ACUTE
"CAFÉ" renders as "CAF ~I"
drivers/mtd/spi-nor/Kconfig
MTD_SPI_NOR_USE_4K_SECTORS
"16 × 4 KiB" renders as "16 ~W 4 KiB"
drivers/net/can/usb/Kconfig
drivers/net/can/peak_canfd/Kconfig
drivers/gpu/drm/panel/Kconfig
drivers/platform/mellanox/Kconfig
kernel/time/Kconfig
crypto/Kconfig
arch/Kconfig
Some of these are clearly wrong (Cyrillic letter), some are
unnecessary (non-breakable space), some are arguable ("CAFÉ" and "16 ×
4 KiB" -- these take advantage of UTF-8 in useful ways).
Not being a charset guru, I dunno if the rendering problem means
my terminal is set incorrectly or if they all need to be changed.
But I think we should address all of them at the same time. If we do
need to avoid UTF-8 in Kconfig help, maybe checkpatch should look for
it.
> BARs that are exposed in other devices that are the part of
> the hierarchy where peer-to-peer DMA is guaranteed by the PCI
> specification to work (ie. anything below a single PCI bridge).
> --
> 1.8.3.1
>
next prev parent reply other threads:[~2022-07-20 17:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 7:22 [PATCH] PCI: eliminate abnormal characters when reads help information of "PCI_P2PDMA" under menuconfig Liu Song
2022-07-20 15:17 ` Randy Dunlap
2022-07-20 17:23 ` Bjorn Helgaas [this message]
2022-08-01 21:56 ` Bjorn Helgaas
2022-08-02 1:11 ` Liu Song
2023-10-06 19:36 ` Bjorn Helgaas
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=20220720172328.GA1647083@bhelgaas \
--to=helgaas@kernel.org \
--cc=apw@canonical.com \
--cc=bhelgaas@google.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liusong@linux.alibaba.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 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).