All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Anup Patel <apatel@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, sunilvl@ventanamicro.com,
	rafael@kernel.org, palmer@dabbelt.com, paul.walmsley@sifive.com,
	alex@ghiti.fr, lenb@kernel.org, atish.patra@linux.dev,
	ajones@ventanamicro.com, anup@brainfault.org, will@kernel.org,
	mark.rutland@arm.com, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Common csr_read_num() and csr_write_num() for RISC-V
Date: Wed, 17 Sep 2025 02:40:12 +0000	[thread overview]
Message-ID: <175807681200.1444719.17820860384159771040.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250818143600.894385-1-apatel@ventanamicro.com>

Hello:

This series was applied to riscv/linux.git (for-next)
by Paul Walmsley <pjw@kernel.org>:

On Mon, 18 Aug 2025 20:05:58 +0530 you wrote:
> Some of the RISC-V drivers (such as RISC-V PMU and ACPI CPPC) need to
> access CSR based on CSR number discovered from somewhere. Add common
> RISC-V csr_read_num() and csr_write_num() functions under arch/riscv
> for such drivers.
> 
> These patches can be found in the riscv_csr_read_num_v2 branch at:
> https://github.com/avpatel/linux.git
> 
> [...]

Here is the summary with links:
  - [v2,1/2] ACPI: RISC-V: Fix FFH_CPPC_CSR error handling
    https://git.kernel.org/riscv/c/5b3706597b90
  - [v2,2/2] RISC-V: Add common csr_read_num() and csr_write_num() functions
    (no matching commit)

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



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Anup Patel <apatel@ventanamicro.com>
Cc: mark.rutland@arm.com, alex@ghiti.fr, rafael@kernel.org,
	anup@brainfault.org, atish.patra@linux.dev,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	palmer@dabbelt.com, paul.walmsley@sifive.com,
	linux-riscv@lists.infradead.org, ajones@ventanamicro.com,
	will@kernel.org, lenb@kernel.org
Subject: Re: [PATCH v2 0/2] Common csr_read_num() and csr_write_num() for RISC-V
Date: Wed, 17 Sep 2025 02:40:12 +0000	[thread overview]
Message-ID: <175807681200.1444719.17820860384159771040.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250818143600.894385-1-apatel@ventanamicro.com>

Hello:

This series was applied to riscv/linux.git (for-next)
by Paul Walmsley <pjw@kernel.org>:

On Mon, 18 Aug 2025 20:05:58 +0530 you wrote:
> Some of the RISC-V drivers (such as RISC-V PMU and ACPI CPPC) need to
> access CSR based on CSR number discovered from somewhere. Add common
> RISC-V csr_read_num() and csr_write_num() functions under arch/riscv
> for such drivers.
> 
> These patches can be found in the riscv_csr_read_num_v2 branch at:
> https://github.com/avpatel/linux.git
> 
> [...]

Here is the summary with links:
  - [v2,1/2] ACPI: RISC-V: Fix FFH_CPPC_CSR error handling
    https://git.kernel.org/riscv/c/5b3706597b90
  - [v2,2/2] RISC-V: Add common csr_read_num() and csr_write_num() functions
    (no matching commit)

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:[~2025-09-17  2:40 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18 14:35 [PATCH v2 0/2] Common csr_read_num() and csr_write_num() for RISC-V Anup Patel
2025-08-18 14:35 ` Anup Patel
2025-08-18 14:35 ` [PATCH v2 1/2] ACPI: RISC-V: Fix FFH_CPPC_CSR error handling Anup Patel
2025-08-18 14:35   ` Anup Patel
2025-08-18 19:26   ` Atish Patra
2025-08-18 19:26     ` Atish Patra
2025-08-19  4:02   ` Nutty.Liu
2025-08-19  4:02     ` Nutty.Liu
2025-08-19  4:25   ` Sunil V L
2025-08-19  4:25     ` Sunil V L
2025-08-20  7:12   ` Alexandre Ghiti
2025-08-20  7:12     ` Alexandre Ghiti
2025-08-18 14:36 ` [PATCH v2 2/2] RISC-V: Add common csr_read_num() and csr_write_num() functions Anup Patel
2025-08-18 14:36   ` Anup Patel
2025-08-18 14:56   ` Andrew Jones
2025-08-18 14:56     ` Andrew Jones
2025-08-18 19:29   ` Atish Patra
2025-08-18 19:29     ` Atish Patra
2025-08-19  3:26   ` Yao Zi
2025-08-19  3:26     ` Yao Zi
2025-08-19  3:30     ` Anup Patel
2025-08-19  3:30       ` Anup Patel
2025-08-19  4:13       ` Yao Zi
2025-08-19  4:13         ` Yao Zi
2025-08-19 11:01         ` Anup Patel
2025-08-19 11:01           ` Anup Patel
2025-08-19  4:04   ` Nutty.Liu
2025-08-19  4:04     ` Nutty.Liu
2025-09-17  2:40 ` patchwork-bot+linux-riscv [this message]
2025-09-17  2:40   ` [PATCH v2 0/2] Common csr_read_num() and csr_write_num() for RISC-V patchwork-bot+linux-riscv

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=175807681200.1444719.17820860384159771040.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=ajones@ventanamicro.com \
    --cc=alex@ghiti.fr \
    --cc=anup@brainfault.org \
    --cc=apatel@ventanamicro.com \
    --cc=atish.patra@linux.dev \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=rafael@kernel.org \
    --cc=sunilvl@ventanamicro.com \
    --cc=will@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.