All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "kernelci.org bot" <bot@kernelci.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the irqchip-fixes tree
Date: Fri, 09 Jul 2021 10:24:40 +0100	[thread overview]
Message-ID: <87czrr3kmf.wl-maz@kernel.org> (raw)
In-Reply-To: <20210709164326.18053838@canb.auug.org.au>

On Fri, 09 Jul 2021 07:43:26 +0100,
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> Hi all,
> 
> After merging the irqchip-fixes tree, today's linux-next build
> (jmr3927_defconfig) failed like this:
> 
> arch/mips/kernel/irq.c:118:9: error: implicit declaration of function ‘irq_resolve_mapping’; did you mean ‘irq_dispose_mapping’? [-Werror=implicit-function-declaration]
> arch/mips/kernel/irq.c:118:7: error: assignment to ‘struct irq_desc *’ from ‘int’ makes pointer from integer without a cast [-Werror=int-conversion]
> 
> Caused by commit
> 
>   f333d6bc4a8b ("irqchip/mips: Fix RCU violation when using irqdomain lookup on interrupt entry")
> 
> Reported by the Kernelci.org bot.
> 
> Not all mips platforms select CONFIG_IRQ_DOMAIN.

Indeed. Thanks for the heads up, now fixed and branch updated.

Cheers,

	M.

-- 
Without deviation from the norm, progress is not possible.

      reply	other threads:[~2021-07-09  9:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-09  6:43 linux-next: build failure after merge of the irqchip-fixes tree Stephen Rothwell
2021-07-09  9:24 ` Marc Zyngier [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=87czrr3kmf.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=bot@kernelci.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.