public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keke Ming <ming.jvle@gmail.com>
To: sanjayembeddedse@gmail.com
Cc: alex@ghiti.fr, anup@brainfault.org, aou@eecs.berkeley.edu,
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
	palmer@dabbelt.com, pjw@kernel.org, tglx@linutronix.de,
	virendrasinhchauhan1206@gmail.com,
	Keke Ming <ming.jvle@gmail.com>
Subject: Re: [PATCH] irqchip/riscv-aplic: adapt to syscore API passing context data
Date: Fri,  2 Jan 2026 17:37:41 +0800	[thread overview]
Message-ID: <20260102093744.66053-1-ming.jvle@gmail.com> (raw)
In-Reply-To: <6eafdd754222e11a43be4bbc3652f7605d47afa6.1766559840.git.sanjayembeddedse@gmail.com>

On Wed, Dec 24, 2025 at 16:41:46 +0530, Sanjay Chitroda wrote:
> The RISC-V APLIC driver started preserving state across suspend/resume,
> but its syscore usage still assumed the old API. Building against
> linux-next after a97fbc3ee3e2 fails because the callbacks don’t receive
> the necessary driver context.

Tested this on riscv64 (cross-compiled on x86_64) using linux-next 
(next-20251219). Without this patch, the build fails with:

drivers/irqchip/irq-riscv-aplic-main.c:111:20: error: initialization of 
‘int (*)(void *)’ from incompatible pointer type ‘int (*)(void)’

This patch correctly fixes the compilation error by updating the APLIC 
driver to the new syscore API.

Tested-by: Keke Ming <ming.jvle@gmail.com>

  reply	other threads:[~2026-01-02  9:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-24 11:11 [PATCH] irqchip/riscv-aplic: adapt to syscore API passing context data Sanjay Chitroda
2026-01-02  9:37 ` Keke Ming [this message]
2026-01-03 15:51 ` Anup Patel
2026-01-09 11:51 ` Thomas Gleixner
2026-01-13 14:51   ` Sanjay Embedded_SE

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=20260102093744.66053-1-ming.jvle@gmail.com \
    --to=ming.jvle@gmail.com \
    --cc=alex@ghiti.fr \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=sanjayembeddedse@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=virendrasinhchauhan1206@gmail.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