From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Marc Zyngier <maz@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the irqchip tree
Date: Thu, 8 Jul 2021 12:18:55 +1000 [thread overview]
Message-ID: <20210708121855.69b5a5f8@canb.auug.org.au> (raw)
In-Reply-To: <20210615210143.2e00d851@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 510 bytes --]
Hi all,
On Tue, 15 Jun 2021 21:01:43 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the irqchip tree, today's linux-next build (htmldocs)
> produced this warning:
>
> kernel/irq/irqdesc.c:692: warning: Excess function parameter 'lookup' description in 'handle_domain_irq'
>
> Introduced by commit
>
> e1c054918c6c ("genirq: Move non-irqdomain handle_domain_irq() handling into ARM's handle_IRQ()")
I am still getting this warning.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-07-08 2:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 11:01 linux-next: build warning after merge of the irqchip tree Stephen Rothwell
2021-07-08 2:18 ` Stephen Rothwell [this message]
2021-07-08 8:10 ` Marc Zyngier
2021-07-08 12:50 ` Stephen Rothwell
2021-07-08 16:32 ` Marc Zyngier
2021-07-08 21:41 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2021-08-13 9:44 Stephen Rothwell
2021-09-03 6:47 ` Stephen Rothwell
2021-09-03 9:00 ` Marc Zyngier
2021-06-07 23:21 Stephen Rothwell
2021-06-08 7:36 ` Marc Zyngier
2018-12-14 3:44 Stephen Rothwell
2018-12-15 9:16 ` Marc Zyngier
2014-11-27 6:28 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=20210708121855.69b5a5f8@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maz@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;
as well as URLs for NNTP newsgroup(s).