All of lore.kernel.org
 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,
	Stefan Agner <stefan@agner.ch>
Subject: linux-next: build failure after merge of the irqchip tree
Date: Mon, 13 Apr 2015 17:05:39 +1000	[thread overview]
Message-ID: <20150413170539.2f20e0a8@canb.auug.org.au> (raw)

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

Hi Jason,

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

kernel/irq/generic-chip.c: In function 'irq_map_generic_chip':
kernel/irq/generic-chip.c:408:2: error: implicit declaration of function 'irq_domain_set_info' [-Werror=implicit-function-declaration]
  irq_domain_set_info(d, virq, hw_irq, chip, gc, ct->handler, NULL, NULL);
  ^

Caused by commit 3f6b2c298240 ("genirq: Generic chip: Support hierarchy
domain").  The only declaration of irq_domain_set_info() depends on
CONFIG_IRQ_DOMAIN_HIERARCHY.

I have used the irqchip tree from next-20150410 fot today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

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

             reply	other threads:[~2015-04-13  7:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13  7:05 Stephen Rothwell [this message]
2015-04-13  9:10 ` linux-next: build failure after merge of the irqchip tree Stefan Agner
2015-04-13 10:50 ` Jason Cooper
2018-10-08  3:06 Stephen Rothwell
2018-10-08  7:06 ` Marc Zyngier
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
2021-04-08  6:35 Stephen Rothwell
2021-04-08  7:56 ` Marc Zyngier
2021-04-08  8:35   ` Jonathan Neuschäfer
2021-06-22  4:15 Stephen Rothwell
2021-06-22  4:15 ` Stephen Rothwell
2022-07-08  4:13 Stephen Rothwell
2022-07-08  7:48 ` Marc Zyngier
2022-07-11  5:42 Stephen Rothwell
2022-07-11  8:15 ` Marc Zyngier
2022-09-29 14:31 broonie
2022-09-29 14:31 ` broonie
2022-09-29 14:40 ` Robin Murphy
2022-09-29 14:40   ` Robin Murphy
2022-09-29 16:22   ` Marc Zyngier
2022-09-29 16:22     ` 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=20150413170539.2f20e0a8@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=jason@lakedaemon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=stefan@agner.ch \
    /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.