From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Kexy Biscuit <kexybiscuit@aosc.io>,
Tiezhu Yang <yangtiezhu@loongson.cn>,
Huacai Chen <chenhuacai@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org
Subject: [PATCH 1/2] docs: ABI: lefi: use literal blocks
Date: Sun, 20 Sep 2026 20:20:47 -0700 [thread overview]
Message-ID: <20260921032048.4060710-1-rdunlap@infradead.org> (raw)
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(-)
--- linux-next-20260918.orig/Documentation/ABI/testing/sysfs-firmware-lefi-boardinfo
+++ linux-next-20260918/Documentation/ABI/testing/sysfs-firmware-lefi-boardinfo
@@ -12,19 +12,19 @@ Description:
requirement and specific for Loongson64, so only add a new
boardinfo.c file in arch/mips/loongson64.
- For example:
+ For example::
- [loongson@linux ~]$ cat /sys/firmware/lefi/boardinfo
- Board Info
- Manufacturer : LEMOTE
- Board Name : LEMOTE-LS3A4000-7A1000-1w-V01-pc
- Family : LOONGSON3
+ [loongson@linux ~]$ cat /sys/firmware/lefi/boardinfo
+ Board Info
+ Manufacturer : LEMOTE
+ Board Name : LEMOTE-LS3A4000-7A1000-1w-V01-pc
+ Family : LOONGSON3
- BIOS Info
- Vendor : Kunlun
- Version : Kunlun-A1901-V4.1.3-20200414093938
- ROM Size : 4 KB
- Release Date : 2020-04-14
+ BIOS Info
+ Vendor : Kunlun
+ Version : Kunlun-A1901-V4.1.3-20200414093938
+ ROM Size : 4 KB
+ Release Date : 2020-04-14
By the way, using dmidecode command can get the similar info if there
exists SMBIOS in firmware, but the fact is that there is no SMBIOS on
next reply other threads:[~2026-09-21 3:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 3:20 Randy Dunlap [this message]
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 ` [PATCH 1/2] docs: ABI: lefi: use literal blocks Thomas Bogendoerfer
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=20260921032048.4060710-1-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--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=tsbogend@alpha.franken.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox