From: Domenico Andreoli <domenico.andreoli@linux.com>
To: dwarves@vger.kernel.org
Subject: [PATCH] Reformat a too long line.
Date: Sat, 1 Feb 2025 15:25:54 +0100 [thread overview]
Message-ID: <Z54u8vZh5tJBzv2V@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 1897 bytes --]
From: Domenico Andreoli <domenico.andreoli@linux.com>
Reformat a too long line.
Signed-off-by: Domenico Andreoli <domenico.andreoli@linux.com>
---
man-pages/pahole.1 | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
Index: b/man-pages/pahole.1
===================================================================
--- a/man-pages/pahole.1
+++ b/man-pages/pahole.1
@@ -304,7 +304,12 @@ Allow using all the BTF features support
.TP
.B \-\-btf_features=FEATURE_LIST
-Encode BTF using the specified feature list, or specify 'default' for all standard features supported. This option can be used as an alternative to using multiple BTF-related options, and 'default' represents the standard set of BTF features that are in use for kernel BTF generation, so is useful as a shortcut for testing the latest set of standard features. However kernel builds will call out specific features rather than using 'default' to ensure that the desired features are enabled regardless of pahole version and associated 'default' set. Supported standard features are
+Encode BTF using the specified feature list, or specify 'default' for all standard features
+supported. This option can be used as an alternative to using multiple BTF-related options,
+and 'default' represents the standard set of BTF features that are in use for kernel BTF generation,
+so is useful as a shortcut for testing the latest set of standard features. However kernel builds
+will call out specific features rather than using 'default' to ensure that the desired features
+are enabled regardless of pahole version and associated 'default' set. Supported standard features are
.nf
encode_force Ignore invalid symbols when encoding BTF; for example
--
rsa4096: 3B10 0CA1 8674 ACBA B4FE FCD2 CE5B CF17 9960 DE13
ed25519: FFB4 0CC3 7F2E 091D F7DA 356E CC79 2832 ED38 CB05
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2025-02-01 14:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-01 14:25 Domenico Andreoli [this message]
2025-02-10 16:54 ` [PATCH] Reformat a too long line Alan Maguire
2025-02-10 20:01 ` Domenico Andreoli
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=Z54u8vZh5tJBzv2V@localhost \
--to=domenico.andreoli@linux.com \
--cc=dwarves@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