public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: 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 tree
Date: Mon, 11 Jul 2022 09:15:19 +0100	[thread overview]
Message-ID: <87mtdgkqug.wl-maz@kernel.org> (raw)
In-Reply-To: <20220711154252.4b88a601@canb.auug.org.au>

On Mon, 11 Jul 2022 06:42:52 +0100,
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> Hi all,
> 
> After merging the irqchip tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> In file included from drivers/gpio/gpio-thunderx.c:18:
> include/asm-generic/msi.h:32:3: error: conflicting types for 'msi_alloc_info_t'; have 'struct msi_alloc_info'
>    32 | } msi_alloc_info_t;
>       |   ^~~~~~~~~~~~~~~~
> In file included from include/linux/gpio/driver.h:15,
>                  from drivers/gpio/gpio-thunderx.c:10:
> arch/x86/include/asm/msi.h:7:31: note: previous declaration of 'msi_alloc_info_t' with type 'msi_alloc_info_t' {aka 'struct irq_alloc_info'}
>     7 | typedef struct irq_alloc_info msi_alloc_info_t;
>       |                               ^~~~~~~~~~~~~~~~
> drivers/gpio/gpio-thunderx.c: In function 'thunderx_gpio_populate_parent_alloc_info':
> drivers/gpio/gpio-thunderx.c:416:34: error: initialization of 'msi_alloc_info_t *' {aka 'struct msi_alloc_info *'} from incompatible pointer type 'msi_alloc_info_t *' {aka 'struct irq_alloc_info *'} [-Werror=incompatible-pointer-types]
>   416 |         msi_alloc_info_t *info = &gfwspec->msiinfo;
>       |                                  ^
> cc1: all warnings being treated as errors
> 
> Caused by commit
> 
>   91a29af413de ("gpio: Remove dynamic allocation from populate_parent_alloc_arg()")
> 
> I have used the irqchip tree from next-20220707 again for today.

Huh. Twice sorry about that one. Patch sent to fix the breakage, and
will push this into irqchip-next shortly.

Thanks,

	M.

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

  reply	other threads:[~2022-07-11  8:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11  5:42 linux-next: build failure after merge of the irqchip tree Stephen Rothwell
2022-07-11  8:15 ` Marc Zyngier [this message]
2022-07-11  8:19 ` [irqchip: irq/irqchip-next] gpio: thunderx: Don't directly include asm-generic/msi.h irqchip-bot for Marc Zyngier
  -- strict thread matches above, loose matches on Subject: below --
2022-09-29 14:31 linux-next: build failure after merge of the irqchip tree broonie
2022-09-29 14:40 ` Robin Murphy
2022-09-29 16:22   ` Marc Zyngier
2022-07-08  4:13 Stephen Rothwell
2022-07-08  7:48 ` Marc Zyngier
2021-06-22  4:15 Stephen Rothwell
2021-04-08  6:35 Stephen Rothwell
2021-04-08  7:56 ` Marc Zyngier
2021-04-08  8:35   ` Jonathan Neuschäfer
2020-03-23  6:59 Stephen Rothwell
2020-03-23  8:08 ` Michal Simek
2020-03-26  6:36 ` Stephen Rothwell
2020-03-26  7:06   ` Michal Simek
2018-10-08  3:06 Stephen Rothwell
2018-10-08  7:06 ` Marc Zyngier
2015-04-13  7:05 Stephen Rothwell
2015-04-13  9:10 ` Stefan Agner
2015-04-13 10:50 ` Jason Cooper

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=87mtdgkqug.wl-maz@kernel.org \
    --to=maz@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox