From: patchwork-bot+linux-riscv@kernel.org
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, corbet@lwn.net,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, conor.dooley@microchip.com,
evan@rivosinc.com, heiko@sntech.de, andy.chiu@sifive.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@rivosinc.com
Subject: Re: [PATCH] Documentation: RISC-V: hwprobe: Fix a formatting error
Date: Wed, 12 Jul 2023 13:50:21 +0000 [thread overview]
Message-ID: <168916982180.8919.16048088678378231987.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230710193329.2742-1-palmer@rivosinc.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Mon, 10 Jul 2023 12:33:30 -0700 you wrote:
> From: Palmer Dabbelt <palmer@rivosinc.com>
>
> I'm not sure what I was trying to do with the ':'s, but they're just
> rendered to HTML which looks odd. This makes "fence.i" look like
> "mvendorid" and such, which is seems reasonable to me.
>
> Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
>
> [...]
Here is the summary with links:
- Documentation: RISC-V: hwprobe: Fix a formatting error
https://git.kernel.org/riscv/c/d6e724d3ef0b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-07-12 13:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 19:33 [PATCH] Documentation: RISC-V: hwprobe: Fix a formatting error Palmer Dabbelt
2023-07-10 19:40 ` Evan Green
2023-07-12 13:39 ` Palmer Dabbelt
2023-07-12 13:50 ` patchwork-bot+linux-riscv [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=168916982180.8919.16048088678378231987.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=andy.chiu@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=corbet@lwn.net \
--cc=evan@rivosinc.com \
--cc=heiko@sntech.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@rivosinc.com \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
/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