From: Jonathan Corbet <corbet@lwn.net>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Michael Ellerman <mpe@ellerman.id.au>,
PowerPC <linuxppc-dev@lists.ozlabs.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Daniel Henrique Barboza <danielhb413@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the powerpc tree
Date: Tue, 24 Aug 2021 07:46:55 -0600 [thread overview]
Message-ID: <877dgbneeo.fsf@meer.lwn.net> (raw)
In-Reply-To: <87v93ve7yg.fsf@linux.ibm.com>
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com> writes:
> Thanks for looking into this. I guess we also need to format the below table?
>
> | 0 8 40
> --|------------
> |
> 0 | 10 20 80
> |
> 8 | 20 10 160
> |
> 40| 80 160 10
>
>
> I don't know how to represent that in the documentation file. A table is
> probably not the right one?
The cheap way out is to put it in a literal block, of course. Sphinx
makes tables pretty easy, though:
https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html#tables
jon
next prev parent reply other threads:[~2021-08-24 13:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 9:55 linux-next: build warning after merge of the powerpc tree Stephen Rothwell
2021-08-23 10:48 ` Stephen Rothwell
2021-08-23 14:19 ` Jonathan Corbet
2021-08-23 23:21 ` Stephen Rothwell
2021-08-24 5:18 ` Aneesh Kumar K.V
2021-08-24 13:46 ` Jonathan Corbet [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-16 3:40 Stephen Rothwell
2023-02-16 18:06 ` Josh Poimboeuf
2023-02-17 1:35 ` Michael Ellerman
2023-02-17 7:05 ` Josh Poimboeuf
2021-04-15 8:52 Stephen Rothwell
2021-04-16 10:54 ` Michael Ellerman
2021-04-14 23:36 Stephen Rothwell
2019-11-13 22:34 Stephen Rothwell
2017-09-04 8:53 Stephen Rothwell
2017-09-04 8:59 ` Cédric Le Goater
2015-10-20 5:21 Stephen Rothwell
2015-10-20 10:06 ` Michael Ellerman
2015-10-20 20:45 ` Stephen Rothwell
2011-05-19 3:19 Stephen Rothwell
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=877dgbneeo.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=aneesh.kumar@linux.ibm.com \
--cc=danielhb413@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).