public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: JeeHeng Sia <jeeheng.sia@starfivetech.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	aou@eecs.berkeley.edu, rafael.j.wysocki@intel.com,
	conor.dooley@microchip.com, palmer@dabbelt.com,
	paul.walmsley@sifive.com, ajones@ventanamicro.com
Subject: Re: [PATCH v2 0/1] Enable SPCR table for console output on RISC-V
Date: Thu, 25 Jul 2024 13:20:39 +0000	[thread overview]
Message-ID: <172191363929.6240.827816040310708972.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240502073751.102093-1-jeeheng.sia@starfivetech.com>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Thu,  2 May 2024 00:37:50 -0700 you wrote:
> The ACPI SPCR code has been used to enable console output for ARM64 and
> X86. The same code can be reused for RISC-V. Furthermore, SPCR table is
> mandated for headless system as outlined in the RISC-V BRS
> Specification, chapter 6.
> 
> Changes in v2:
> - Added code to handle early_init_dt_scan_chosen_stdout().
> 
> [...]

Here is the summary with links:
  - [v2,1/1] RISC-V: ACPI: Enable SPCR table for console output on RISC-V
    https://git.kernel.org/riscv/c/38738947db38

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



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

      parent reply	other threads:[~2024-07-25 13:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-02  7:37 [PATCH v2 0/1] Enable SPCR table for console output on RISC-V Sia Jee Heng
2024-05-02  7:37 ` [PATCH v2 1/1] RISC-V: ACPI: " Sia Jee Heng
2024-07-09  4:49   ` Sunil V L
2024-07-25 13:20 ` 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=172191363929.6240.827816040310708972.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=ajones@ventanamicro.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor.dooley@microchip.com \
    --cc=jeeheng.sia@starfivetech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=rafael.j.wysocki@intel.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