From: tip-bot for Mathieu Desnoyers <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org,
mathieu.desnoyers@efficios.com, torvalds@linux-foundation.org,
corbet@lwn.net, hpa@zytor.com, peterz@infradead.org,
tglx@linutronix.de
Subject: [tip:core/core] Documentation/features: Allow comments in arch features files
Date: Sun, 11 Feb 2018 04:12:35 -0800 [thread overview]
Message-ID: <tip-26be459c9c4431984ad4b576f975ce6d3184d71d@git.kernel.org> (raw)
In-Reply-To: <1518282058-24226-1-git-send-email-mathieu.desnoyers@efficios.com>
Commit-ID: 26be459c9c4431984ad4b576f975ce6d3184d71d
Gitweb: https://git.kernel.org/tip/26be459c9c4431984ad4b576f975ce6d3184d71d
Author: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
AuthorDate: Sat, 10 Feb 2018 12:00:58 -0500
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Sun, 11 Feb 2018 12:18:50 +0100
Documentation/features: Allow comments in arch features files
The list-arch.sh script considers lines beginning with "#" as match for
the feature table.
Given that those tables are never in lines beginning with "#",
add a reverse grep on "^#" when matching the "ok/TODO" state of
the architecture.
This allows adding comments within the feature files, for instance
describing the architecture requirements for the feature in each
architecture.
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-doc@vger.kernel.org
Link: http://lkml.kernel.org/r/1518282058-24226-1-git-send-email-mathieu.desnoyers@efficios.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
Documentation/features/list-arch.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/features/list-arch.sh b/Documentation/features/list-arch.sh
index c16b5b5..1ec47c3 100755
--- a/Documentation/features/list-arch.sh
+++ b/Documentation/features/list-arch.sh
@@ -17,7 +17,7 @@ for F in */*/arch-support.txt; do
N=$(grep -h "^# Feature name:" $F | cut -c25-)
C=$(grep -h "^# Kconfig:" $F | cut -c25-)
D=$(grep -h "^# description:" $F | cut -c25-)
- S=$(grep -hw $ARCH $F | cut -d\| -f3)
+ S=$(grep -hv "^#" $F | grep -w $ARCH | cut -d\| -f3)
printf "%10s/%-22s:%s| %35s # %s\n" "$SUBSYS" "$N" "$S" "$C" "$D"
done
next prev parent reply other threads:[~2018-02-12 1:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 20:30 [PATCH for 4.16] membarrier-sync-core: Document architecture support Mathieu Desnoyers
2018-02-10 11:47 ` Ingo Molnar
2018-02-10 17:00 ` [PATCH for 4.16] Documentation: Allow comments in arch features files Mathieu Desnoyers
2018-02-11 12:12 ` tip-bot for Mathieu Desnoyers [this message]
2018-02-11 12:08 ` [tip:sched/urgent] membarrier-sync-core: Document architecture support tip-bot for Mathieu Desnoyers
2018-02-11 12:13 ` [tip:core/core] Documentation/features, membarriers: Document membarrier-sync-core " tip-bot for Mathieu Desnoyers
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=tip-26be459c9c4431984ad4b576f975ce6d3184d71d@git.kernel.org \
--to=tipbot@zytor.com \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
Powered by JetHome