Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] RISC-V Patches for the 6.10 Merge Window, Part 1
Date: Wed, 22 May 2024 17:18:56 +0100	[thread overview]
Message-ID: <20240522-confused-epic-03a59031e645@spud> (raw)
In-Reply-To: <mhng-e73e59bf-92fc-4122-9f9e-a329d20eba55@palmer-ri-x1c9>


[-- Attachment #1.1: Type: text/plain, Size: 1265 bytes --]

On Wed, May 22, 2024 at 09:13:28AM -0700, Palmer Dabbelt wrote:
> This first one isn't showing up in a in-flight merge `git diff`, but it looks
> pretty straight-forward
> 
>     diff --git a/Documentation/rust/arch-support.rst b/Documentation/rust/arch-support.rst
>     index c9137710633a..4d1495ded2aa 100644
>     --- a/Documentation/rust/arch-support.rst
>     +++ b/Documentation/rust/arch-support.rst
>     @@ -16,7 +16,8 @@ support corresponds to ``S`` values in the ``MAINTAINERS`` file.
>      Architecture   Level of support  Constraints
>      =============  ================  ==============================================
>      ``arm64``      Maintained        Little Endian only.
>     -``loongarch``  Maintained        \-
>     +``loongarch``  Maintained        -

I think this is actually the wrong resolution, and the \ should be kept
as it was added as a fix in commit 01848eee20c6 ("docs: rust: fix improper
rendering in Arch Support page").

Cheers,
Conor.

>     +``riscv``      Maintained        ``riscv64`` only.
>      ``um``         Maintained        ``x86_64`` only.
>      ``x86``        Maintained        ``x86_64`` only.
>      =============  ================  ==============================================

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2024-05-22 16:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22 16:13 [GIT PULL] RISC-V Patches for the 6.10 Merge Window, Part 1 Palmer Dabbelt
2024-05-22 16:18 ` Conor Dooley [this message]
2024-05-22 18:05 ` pr-tracker-bot
2024-05-22 23:32 ` patchwork-bot+linux-riscv
2024-05-22 23:51 ` patchwork-bot+linux-riscv
2024-05-23  3:45 ` Masahiro Yamada
2024-05-23 11:59   ` Michael Ellerman
2024-05-24  5:06     ` Masahiro Yamada

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=20240522-confused-epic-03a59031e645@spud \
    --to=conor@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@rivosinc.com \
    --cc=torvalds@linux-foundation.org \
    /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