[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190617181116.GA17114@kroah.com>
Date: Mon, 17 Jun 2019 20:11:16 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Mauro Carvalho Chehab <mchehab+samsung@...nel.org>
Cc: Linux Doc Mailing List <linux-doc@...r.kernel.org>,
Jonathan Corbet <corbet@....net>,
Mauro Carvalho Chehab <mchehab@...radead.org>,
linux-kernel@...r.kernel.org,
ksummit-discuss@...ts.linuxfoundation.org
Subject: Re: [PATCH RFC] scripts: add a script to handle
Documentation/features
On Mon, Jun 17, 2019 at 03:05:07PM -0300, Mauro Carvalho Chehab wrote:
> The Documentation/features contains a set of parseable files.
> It is not worth converting them to ReST format, as they're
> useful the way it is. It is, however, interesting to parse
> them and produce output on different formats:
>
> 1) Output the contents of a feature in ReST format;
>
> 2) Output what features a given architecture supports;
>
> 3) Output a matrix with features x architectures.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@...nel.org>
> ---
>
> As commented at KS mailing list, converting the Documentation/features
> file to ReST may not be the best way to handle it.
>
> This script allows validating the features files and to generate ReST files
> on three different formats.
>
> The goal is to support it via a sphinx extension, in order to be able to add
> the features inside the Kernel documentation.
>
> scripts/get_feat.pl | 470 ++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 470 insertions(+)
> create mode 100755 scripts/get_feat.pl
>
> diff --git a/scripts/get_feat.pl b/scripts/get_feat.pl
> new file mode 100755
> index 000000000000..c5a267b12f49
> --- /dev/null
> +++ b/scripts/get_feat.pl
> @@ -0,0 +1,470 @@
> +#!/usr/bin/perl
> +
No SPDX line :(
Powered by blists - more mailing lists