From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: linux-next: build failure after merge of the gpio-lw tree
Date: Fri, 6 Jul 2012 16:14:55 +1000 [thread overview]
Message-ID: <20120706161455.dd899154fbc8a79ee530572f@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 381 bytes --]
Hi Linus,
After merging the gpio-lw tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: "irq_set_chip_and_handler_name" [drivers/gpio/gpio-pcf857x.ko] undefined!
ERROR: "dummy_irq_chip" [drivers/gpio/gpio-pcf857x.ko] undefined!
I have dropped the gpio-lw tree for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2012-07-06 6:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 6:14 Stephen Rothwell [this message]
2012-07-06 7:01 ` linux-next: build failure after merge of the gpio-lw tree Linus Walleij
2012-07-06 8:55 ` Kuninori Morimoto
2012-07-08 19:14 ` Linus Walleij
2012-07-09 2:04 ` Kuninori Morimoto
2012-07-09 2:05 ` [PATCH 1/2] genirq: export irq_set_chip_and_handler_name() Kuninori Morimoto
2012-07-09 2:06 ` [PATCH 2/2] genirq: export dummy_irq_chip Kuninori Morimoto
2012-07-09 20:34 ` linux-next: build failure after merge of the gpio-lw tree Linus Walleij
2012-07-24 3:56 ` Kuninori Morimoto
2012-07-31 5:38 ` [PATCH 0/2][resend] genirq: export patches Kuninori Morimoto
2012-07-31 5:39 ` [PATCH 1/2][resend] genirq: export irq_set_chip_and_handler_name() Kuninori Morimoto
2012-07-31 5:39 ` [PATCH 2/2][resend] genirq: export dummy_irq_chip Kuninori Morimoto
2012-08-22 5:03 ` linux-next: build failure after merge of the gpio-lw tree Kuninori Morimoto
2012-08-23 21:43 ` Linus Walleij
2012-08-27 1:16 ` Kuninori Morimoto
2013-01-18 3:03 Stephen Rothwell
2013-01-18 8:02 ` Shawn Guo
2013-01-18 23:40 ` Stephen Rothwell
2013-01-21 6:20 ` Shawn Guo
2013-01-21 5:53 ` 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=20120706161455.dd899154fbc8a79ee530572f@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linus.walleij@linaro.org \
--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).