public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Andrea della Porta <andrea.porta@suse.com>,
	Florian Fainelli <florian.fainelli@broadcom.com>,
	"Jiri Slaby (SUSE)" <jirislaby@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the broadcom tree
Date: Tue, 3 Jun 2025 12:20:12 +1000	[thread overview]
Message-ID: <20250603122012.4ff9c5ea@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1871 bytes --]

Hi all,

After merging the broadcom tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/pinctrl/pinctrl-rp1.c: In function 'rp1_gpio_irq_handler':
drivers/pinctrl/pinctrl-rp1.c:385:36: error: implicit declaration of function 'irq_linear_revmap' [-Wimplicit-function-declaration]
  385 |                 generic_handle_irq(irq_linear_revmap(pc->gpio_chip.irq.domain,
      |                                    ^~~~~~~~~~~~~~~~~

Caused by commit

  f4b3c1c25d39 ("pinctrl: rp1: Implement RaspberryPi RP1 gpio support")

interatcing with commit

  14ebb11ba895 ("irqdomain: Drop irq_linear_revmap()")

from Linus' tree.

I have applied the following merge fix patch.

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Tue, 3 Jun 2025 12:07:49 +1000
Subject: [PATCH] fix up for "pinctrl: rp1: Implement RaspberryPi RP1 gpio
 support"

interacting with commit

  14ebb11ba895 ("irqdomain: Drop irq_linear_revmap()")

from Linus' tree.

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 drivers/pinctrl/pinctrl-rp1.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/pinctrl/pinctrl-rp1.c b/drivers/pinctrl/pinctrl-rp1.c
index 7ff2db0320ba..8c70ea0fc160 100644
--- a/drivers/pinctrl/pinctrl-rp1.c
+++ b/drivers/pinctrl/pinctrl-rp1.c
@@ -382,7 +382,7 @@ static void rp1_gpio_irq_handler(struct irq_desc *desc)
 		struct rp1_pin_info *pin = rp1_get_pin(chip, bit_pos);
 
 		regmap_field_write(pin->gpio[RP1_GPIO_CTRL_IRQRESET_SET], 1);
-		generic_handle_irq(irq_linear_revmap(pc->gpio_chip.irq.domain,
+		generic_handle_irq(irq_find_mapping(pc->gpio_chip.irq.domain,
 						     bank->gpio_offset + bit_pos));
 	}
 
-- 
2.47.2

-- 
Cheers,
Stephen Rothwell

P.S. did you get the message about "no new stuff in -next until the end
of the merge window"?

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2025-06-03  2:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-03  2:20 Stephen Rothwell [this message]
2025-06-05  3:06 ` linux-next: build failure after merge of the broadcom tree Florian Fainelli
  -- strict thread matches above, loose matches on Subject: below --
2022-06-28  0:07 Stephen Rothwell

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=20250603122012.4ff9c5ea@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=andrea.porta@suse.com \
    --cc=f.fainelli@gmail.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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