linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jason Cooper <jason@lakedaemon.net>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
Subject: linux-next: build warning after merge of the irqchip tree
Date: Thu, 27 Nov 2014 17:28:22 +1100	[thread overview]
Message-ID: <20141127172822.593adbd2@canb.auug.org.au> (raw)

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

Hi Jason,

After merging the irqchip tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:

include/linux/irqchip/arm-gic.h:109:53: warning: its scope is only this definition or declaration, which is probably not what you want
In file included from arch/arm/mach-ux500/pm.c:13:0:
include/linux/irqchip/arm-gic.h:109:53: warning: 'struct irq_domain' declared inside parameter list
 int gicv2m_of_init(struct device_node *node, struct irq_domain *parent);
                                                     ^

and many more similar.

Introduced by commit 853a33ce6932 ("irqchip: gic-v2m: Add support for
ARM GICv2m MSI(-X) doorbell").

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

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

             reply	other threads:[~2014-11-27  6:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27  6:28 Stephen Rothwell [this message]
2014-11-28  4:46 ` [PATCH] irqchip: gic: Remove warning by including linux/irqdomain.h Jason Cooper
2018-12-14  3:44 linux-next: build warning after merge of the irqchip tree Stephen Rothwell
2018-12-15  9:16 ` Marc Zyngier
2021-06-07 23:21 Stephen Rothwell
2021-06-08  7:36 ` Marc Zyngier
2021-06-15 11:01 Stephen Rothwell
2021-07-08  2:18 ` Stephen Rothwell
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
2021-08-13  9:44 Stephen Rothwell
2021-09-03  6:47 ` Stephen Rothwell
2021-09-03  9:00   ` Marc Zyngier

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=20141127172822.593adbd2@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=Suravee.Suthikulpanit@amd.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.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).