From: "tip-bot2 for Ahmed S. Darwish" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: "Ahmed S. Darwish" <darwi@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/misc] tools/x86/kcpuid: Strip bitfield names leading/trailing whitespace
Date: Fri, 02 Aug 2024 07:28:45 -0000 [thread overview]
Message-ID: <172258372520.2215.2625975190952358820.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20240718134755.378115-6-darwi@linutronix.de>
The following commit has been merged into the x86/misc branch of tip:
Commit-ID: 9ecbc60a5ede928abdd2b152d828ae0ea8a1e3ed
Gitweb: https://git.kernel.org/tip/9ecbc60a5ede928abdd2b152d828ae0ea8a1e3ed
Author: Ahmed S. Darwish <darwi@linutronix.de>
AuthorDate: Thu, 18 Jul 2024 15:47:45 +02:00
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitterDate: Fri, 02 Aug 2024 09:17:19 +02:00
tools/x86/kcpuid: Strip bitfield names leading/trailing whitespace
While parsing and saving bitfield names from the CSV file, an extra
leading space is copied verbatim. That extra space is not a big issue
now, but further commits will add a new CSV file with much more padding
for the bitfield's name column.
Strip leading/trailing whitespaces while saving bitfield names.
Signed-off-by: Ahmed S. Darwish <darwi@linutronix.de>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/all/20240718134755.378115-6-darwi@linutronix.de
---
tools/arch/x86/kcpuid/kcpuid.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/arch/x86/kcpuid/kcpuid.c b/tools/arch/x86/kcpuid/kcpuid.c
index 581d28c..c4f0ace 100644
--- a/tools/arch/x86/kcpuid/kcpuid.c
+++ b/tools/arch/x86/kcpuid/kcpuid.c
@@ -379,7 +379,7 @@ static int parse_line(char *line)
if (start)
bdesc->start = strtoul(start, NULL, 0);
- strcpy(bdesc->simp, tokens[4]);
+ strcpy(bdesc->simp, strtok(tokens[4], " \t"));
strcpy(bdesc->detail, tokens[5]);
return 0;
next prev parent reply other threads:[~2024-08-02 7:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 13:45 [ANNOUNCE] x86-cpuid.org: A machine-readable CPUID repository Ahmed S. Darwish
2024-07-18 13:47 ` [PATCH v1 0/9] tools/x86/kcpuid: Complete the CPUID database Ahmed S. Darwish
2024-07-18 13:47 ` [PATCH v1 1/9] tools/x86/kcpuid: Remove unused variable Ahmed S. Darwish
2024-08-02 7:28 ` [tip: x86/misc] " tip-bot2 for Ahmed S. Darwish
2024-07-18 13:47 ` [PATCH v1 2/9] tools/x86/kcpuid: Properly align long-description columns Ahmed S. Darwish
2024-08-02 7:28 ` [tip: x86/misc] " tip-bot2 for Ahmed S. Darwish
2024-07-18 13:47 ` [PATCH v1 3/9] tools/x86/kcpuid: Set max possible subleaves count to 64 Ahmed S. Darwish
2024-08-02 7:28 ` [tip: x86/misc] " tip-bot2 for Ahmed S. Darwish
2024-07-18 13:47 ` [PATCH v1 4/9] tools/x86/kcpuid: Protect against faulty "max subleaf" values Ahmed S. Darwish
2024-08-02 7:28 ` [tip: x86/misc] " tip-bot2 for Ahmed S. Darwish
2024-07-18 13:47 ` [PATCH v1 5/9] tools/x86/kcpuid: Strip bitfield names leading/trailing whitespace Ahmed S. Darwish
2024-08-02 7:28 ` tip-bot2 for Ahmed S. Darwish [this message]
2024-07-18 13:47 ` [PATCH v1 6/9] tools/x86/kcpuid: Recognize all leaves with subleaves Ahmed S. Darwish
2024-08-02 7:28 ` [tip: x86/misc] " tip-bot2 for Ahmed S. Darwish
2024-07-18 13:47 ` [PATCH v1 7/9] tools/x86/kcpuid: Parse subleaf ranges if provided Ahmed S. Darwish
2024-08-02 7:28 ` [tip: x86/misc] " tip-bot2 for Ahmed S. Darwish
2024-07-18 13:47 ` [PATCH v1 8/9] tools/x86/kcpuid: Introduce a complete cpuid bitfields CSV file Ahmed S. Darwish
2024-08-02 7:28 ` [tip: x86/misc] " tip-bot2 for Ahmed S. Darwish
2024-07-18 13:47 ` [PATCH v1 9/9] MAINTAINERS: Add x86 cpuid database entry Ahmed S. Darwish
2024-08-02 7:28 ` [tip: x86/misc] " tip-bot2 for Ahmed S. Darwish
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=172258372520.2215.2625975190952358820.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=darwi@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®