mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Antony Pavlov <>
Cc: Ahmad Fatoum <>
Subject: [PATCH 1/7] Documentation: OKUD Max9331: fix sphinx warning
Date: Mon, 12 Sep 2022 11:44:24 +0300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

sphinx warning:

  Documentation/boards/mips/max9331.rst:129: WARNING:
    Pygments lexer name 'assembly' is not known

Use pygments lexer for Gas (AT&T) assembly code, see
for details.

Signed-off-by: Antony Pavlov <>
 Documentation/boards/mips/max9331.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/boards/mips/max9331.rst b/Documentation/boards/mips/max9331.rst
index f09dabc2da1..f7529f9874d 100644
--- a/Documentation/boards/mips/max9331.rst
+++ b/Documentation/boards/mips/max9331.rst
@@ -126,7 +126,7 @@ it jump to 0x9f020000 where the first instruction of barebox.
 This is usefull when debug with jtag or choosing different bootloaders.
 or even boot kernel without bootloader.
-.. code-block:: assembly
+.. code-block:: asm
  lui  ra, 0x9f02
  jr   ra

  reply	other threads:[~2022-09-12  8:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-12  8:44 [PATCH 0/7] Documentation misc fixes Antony Pavlov
2022-09-12  8:44 ` Antony Pavlov [this message]
2022-09-12  8:44 ` [PATCH 2/7] Documentation: Altera SOCFPGA FPGA Manager: fix sphinx error Antony Pavlov
2022-09-12  8:44 ` [PATCH 3/7] Documentation: Altera FPGAs in passive-serial mode: fix sphinx issues Antony Pavlov
2022-09-12  8:44 ` [PATCH 4/7] Documentation: barebox DT aliases: " Antony Pavlov
2022-09-12  8:44 ` [PATCH 5/7] Documentation: barebox environment: fix list rendering Antony Pavlov
2022-09-12  8:44 ` [PATCH 6/7] Documentation: Common leds properties: fix 'panic-indicator' list entry rendering Antony Pavlov
2022-09-12  8:44 ` [PATCH 7/7] Documentation: Voltage/Current Regulators: fix sphinx error Antony Pavlov
2022-09-13  8:10 ` [PATCH 0/7] Documentation misc fixes Sascha Hauer

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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