public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn•net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel•org>
Cc: "Rich Felker" <dalias@libc•org>,
	linux-ia64@vger•kernel.org,
	"Linux Doc Mailing List" <linux-doc@vger•kernel.org>,
	x86@kernel•org, linux-mips@vger•kernel.org,
	"James E.J. Bottomley" <James.Bottomley@HansenPartnership•com>,
	"Paul Mackerras" <paulus@samba•org>,
	"H. Peter Anvin" <hpa@zytor•com>,
	linux-riscv@lists•infradead.org, "Will Deacon" <will@kernel•org>,
	"Thomas Gleixner" <tglx@linutronix•de>,
	"Jonas Bonn" <jonas@southpole•se>,
	linux-s390@vger•kernel.org,
	"Yoshinori Sato" <ysato@users•sourceforge.jp>,
	"Helge Deller" <deller@gmx•de>,
	linux-sh@vger•kernel.org,
	"Christian Borntraeger" <borntraeger@de•ibm.com>,
	"Ingo Molnar" <mingo@redhat•com>,
	"Catalin Marinas" <catalin.marinas@arm•com>,
	"Fenghua Yu" <fenghua.yu@intel•com>,
	"Albert Ou" <aou@eecs•berkeley.edu>,
	"Kees Cook" <keescook@chromium•org>,
	"Vasily Gorbik" <gor@linux•ibm.com>,
	"Heiko Carstens" <hca@linux•ibm.com>,
	"Jonathan Neuschäfer" <j.neuschaefer@gmx•net>,
	"Stefan Kristiansson" <stefan.kristiansson@saunalahti•fi>,
	"Tony Luck" <tony.luck@intel•com>,
	"Borislav Petkov" <bp@alien8•de>,
	"Paul Walmsley" <paul.walmsley@sifive•com>,
	"Stafford Horne" <shorne@gmail•com>,
	"Daniel W. S. Almeida" <dwlsalmeida@gmail•com>,
	linux-arm-kernel@lists•infradead.org,
	"Thomas Bogendoerfer" <tsbogend@alpha•franken.de>,
	linux-parisc@vger•kernel.org,
	"Andrew Cooper" <andrew.cooper3@citrix•com>,
	linux-kernel@vger•kernel.org, openrisc@lists•librecores.org,
	"Palmer Dabbelt" <palmer@dabbelt•com>,
	"Masami Hiramatsu" <mhiramat@kernel•org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation•org>,
	linuxppc-dev@lists•ozlabs.org
Subject: Re: [PATCH 0/6] Add documentation for Documentation/features at the built docs
Date: Thu, 3 Dec 2020 15:36:42 -0700	[thread overview]
Message-ID: <20201203153642.594afd85@lwn.net> (raw)
In-Reply-To: <cover.1606748711.git.mchehab+huawei@kernel.org>

On Mon, 30 Nov 2020 16:36:29 +0100
Mauro Carvalho Chehab <mchehab+huawei@kernel•org> wrote:

> This series got already submitted last year:
> 
>    https://lore.kernel.org/lkml/cover.1561222784.git.mchehab+samsung@kernel.org/
> 
> Yet, on that time, there were too many other patches related to ReST
> conversion floating around. So, at the end, I guess this one got missed.
> 
> So, I did a rebase on the top of upstream, and added a few new changes.

OK, I've gone ahead and applied these; it gains me a new trivial conflict
with x86, but so be it...

That said, I think that the RST table formatting could be *way* improved.
The current tables are all white space and hard to make sense of.  What if
we condensed the information?  Just looking at the first entry in
Documentation/admin-guide/features.html, perhaps it could look like:

    FEATURE	KCONFIG/DESCRIPTION		STATUS

    cBPF-JIT	HAVE_CBPF_JIT			TODO: alpha, arc, arm...
    						ok: mips, powerpc, ...
		arch supports cBPF JIT
		optimizations

The result would be far more compact and easy to read, IMO.  I may get
around to giving this a try if (hint :) nobody else gets there first.

Thanks,

jon

      parent reply	other threads:[~2020-12-03 22:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30 15:36 [PATCH 0/6] Add documentation for Documentation/features at the built docs Mauro Carvalho Chehab
2020-11-30 15:36 ` [PATCH 6/6] docs: archis: add a per-architecture features list Mauro Carvalho Chehab
2020-12-03 22:36 ` Jonathan Corbet [this message]

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=20201203153642.594afd85@lwn.net \
    --to=corbet@lwn$(echo .)net \
    --cc=James.Bottomley@HansenPartnership$(echo .)com \
    --cc=andrew.cooper3@citrix$(echo .)com \
    --cc=aou@eecs$(echo .)berkeley.edu \
    --cc=borntraeger@de$(echo .)ibm.com \
    --cc=bp@alien8$(echo .)de \
    --cc=catalin.marinas@arm$(echo .)com \
    --cc=dalias@libc$(echo .)org \
    --cc=deller@gmx$(echo .)de \
    --cc=dwlsalmeida@gmail$(echo .)com \
    --cc=fenghua.yu@intel$(echo .)com \
    --cc=gor@linux$(echo .)ibm.com \
    --cc=gregkh@linuxfoundation$(echo .)org \
    --cc=hca@linux$(echo .)ibm.com \
    --cc=hpa@zytor$(echo .)com \
    --cc=j.neuschaefer@gmx$(echo .)net \
    --cc=jonas@southpole$(echo .)se \
    --cc=keescook@chromium$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-doc@vger$(echo .)kernel.org \
    --cc=linux-ia64@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-mips@vger$(echo .)kernel.org \
    --cc=linux-parisc@vger$(echo .)kernel.org \
    --cc=linux-riscv@lists$(echo .)infradead.org \
    --cc=linux-s390@vger$(echo .)kernel.org \
    --cc=linux-sh@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=mchehab+huawei@kernel$(echo .)org \
    --cc=mhiramat@kernel$(echo .)org \
    --cc=mingo@redhat$(echo .)com \
    --cc=openrisc@lists$(echo .)librecores.org \
    --cc=palmer@dabbelt$(echo .)com \
    --cc=paul.walmsley@sifive$(echo .)com \
    --cc=paulus@samba$(echo .)org \
    --cc=shorne@gmail$(echo .)com \
    --cc=stefan.kristiansson@saunalahti$(echo .)fi \
    --cc=tglx@linutronix$(echo .)de \
    --cc=tony.luck@intel$(echo .)com \
    --cc=tsbogend@alpha$(echo .)franken.de \
    --cc=will@kernel$(echo .)org \
    --cc=x86@kernel$(echo .)org \
    --cc=ysato@users$(echo .)sourceforge.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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