From: patchwork-bot+linux-riscv@kernel.org
To: Sunil V L <sunilvl@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com,
aou@eecs.berkeley.edu, anup@brainfault.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
atishp@atishpatra.org, will@kernel.org
Subject: Re: [PATCH v2 -next 0/2] RISC-V ACPI: Assorted fixes
Date: Tue, 20 Jun 2023 01:00:23 +0000 [thread overview]
Message-ID: <168722282377.22807.11943189274896706189.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230607112417.782085-1-sunilvl@ventanamicro.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 7 Jun 2023 16:54:15 +0530 you wrote:
> This series fixes couple of issues required to complete the previously
> merged basic ACPI support series.
>
> 1) Kernel test bot has found a new warning using the sparse tool. Though
> I believe this warning exists for other architectures also,
> I don't see an issue fixing this for RISC-V.
>
> [...]
Here is the summary with links:
- [v2,-next,1/2] RISC-V: ACPI : Fix for usage of pointers in different address space
https://git.kernel.org/riscv/c/3b426d4b5b14
- [v2,-next,2/2] RISC-V/perf: Use standard interface to get INTC domain
https://git.kernel.org/riscv/c/ca7473cb8312
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
prev parent reply other threads:[~2023-06-20 1:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 11:24 [PATCH v2 -next 0/2] RISC-V ACPI: Assorted fixes Sunil V L
2023-06-07 11:24 ` [PATCH v2 -next 1/2] RISC-V: ACPI : Fix for usage of pointers in different address space Sunil V L
2023-06-07 11:24 ` [PATCH v2 -next 2/2] RISC-V/perf: Use standard interface to get INTC domain Sunil V L
2023-06-07 23:19 ` Atish Patra
2023-06-07 18:20 ` [PATCH v2 -next 0/2] RISC-V ACPI: Assorted fixes Conor Dooley
2023-06-19 22:07 ` Palmer Dabbelt
2023-06-20 1:00 ` 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=168722282377.22807.11943189274896706189.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@atishpatra.org \
--cc=linux-arm-kernel@lists.infradead.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox