From: patchwork-bot+linux-riscv@kernel.org
To: Jennifer Berringer <jberring@redhat.com>
Cc: linux-riscv@lists.infradead.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, dlan@kernel.org,
pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
alex@ghiti.fr, hendrik.hamerlinck@hammernet.be,
devicetree@vger.kernel.org, spacemit@lists.linux.dev,
linux-kernel@vger.kernel.org, legoll@online.fr
Subject: Re: [PATCH v2] riscv: dts: spacemit: set console baud rate on OrangePi RV2
Date: Sun, 01 Nov 2026 22:17:15 +0000 [thread overview]
Message-ID: <179357143579.2624073.15759180385936074030.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260929120227.1791356-1-jberring@redhat.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Yixun Lan <dlan@kernel.org>:
On Tue, 29 Sep 2026 08:02:27 -0400 you wrote:
> Set the baud rate to 115200, matching what is used by U-Boot on this
> platform so that the console is usable even when console options are not
> specified in cmdline.
>
> Fixes: bab8dea259100 ("riscv: dts: spacemit: Add OrangePi RV2 board device tree")
> Tested-by: Vincent Legoll <legoll@online.fr>
> Reviewed-by: Yixun Lan <dlan@kernel.org>
> Signed-off-by: Jennifer Berringer <jberring@redhat.com>
>
> [...]
Here is the summary with links:
- [v2] riscv: dts: spacemit: set console baud rate on OrangePi RV2
https://git.kernel.org/riscv/c/789eed2d8bfa
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:[~2026-11-01 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 12:02 Jennifer Berringer
2026-09-30 7:34 ` Iker Pedrosa
2026-10-02 11:16 ` Yixun Lan
2026-11-01 22:17 ` 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=179357143579.2624073.15759180385936074030.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@kernel.org \
--cc=hendrik.hamerlinck@hammernet.be \
--cc=jberring@redhat.com \
--cc=krzk+dt@kernel.org \
--cc=legoll@online.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
/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
all inboxes | Powered by JetHome®