From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, Kexy Biscuit <kexybiscuit@aosc.io>,
Tiezhu Yang <yangtiezhu@loongson.cn>,
Huacai Chen <chenhuacai@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
linux-mips@vger.kernel.org
Subject: Re: [PATCH 1/2] docs: ABI: lefi: use literal blocks
Date: Sun, 27 Sep 2026 10:42:49 +0200 [thread overview]
Message-ID: <arjXCdB-3SYoQhTc@alpha.franken.de> (raw)
In-Reply-To: <20260921032048.4060710-1-rdunlap@infradead.org>
On Sun, Sep 20, 2026 at 08:20:47PM -0700, Randy Dunlap wrote:
> Use literal blocks for console I/O examples so that the lines
> aren't run together in the produced html.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Cc: Kexy Biscuit <kexybiscuit@aosc.io>
> Cc: Tiezhu Yang <yangtiezhu@loongson.cn>
> Cc: Huacai Chen <chenhuacai@kernel.org>
> Cc: Jiaxun Yang <jiaxun.yang@flygoat.com>
> Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> Cc: linux-mips@vger.kernel.org
>
> Documentation/ABI/testing/sysfs-firmware-lefi-boardinfo | 22 +++++-----
> 1 file changed, 11 insertions(+), 11 deletions(-)
applied to mips-next
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2026-09-27 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 3:20 [PATCH 1/2] docs: ABI: lefi: use literal blocks Randy Dunlap
2026-09-21 3:20 ` [PATCH 2/2] docs: ABI: lefi: drop "ROM Size" in sysfs file doc Randy Dunlap
2026-09-27 8:43 ` Thomas Bogendoerfer
2026-09-27 8:42 ` Thomas Bogendoerfer [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=arjXCdB-3SYoQhTc@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=chenhuacai@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=kexybiscuit@aosc.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=yangtiezhu@loongson.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.