From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: linux-next: build failure after merge of the mfd-lj tree
Date: Tue, 20 May 2014 18:01:59 +1000 [thread overview]
Message-ID: <20140520180159.3a70193c@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 612 bytes --]
Hi Lee,
After merging the mfd-lj tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/mfd/stmpe.c: In function 'stmpe_irq_init':
drivers/mfd/stmpe.c:1000:15: error: 'struct stmpe' has no member named 'irq_base'
base = stmpe->irq_base;
^
Caused by commit 3ba1d516d5fe ("mfd: stmpe: root out static GPIO and
IRQ assignments").
This is exactly the same error and commit I reported against the gpio
tree on Friday. Why has it come back?
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2014-05-20 8:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 8:01 Stephen Rothwell [this message]
2014-05-22 22:15 ` linux-next: build failure after merge of the mfd-lj tree Linus Walleij
2014-05-23 8:50 ` [GIT PULL v2] mfd/gpio: New pull request with irq_base removed Lee Jones
-- strict thread matches above, loose matches on Subject: below --
2014-06-19 5:20 linux-next: build failure after merge of the mfd-lj tree Stephen Rothwell
2014-04-24 3:01 Stephen Rothwell
2014-02-14 2:42 Stephen Rothwell
2014-02-17 3:14 ` Stephen Rothwell
2014-02-20 4:05 ` Stephen Rothwell
2014-02-25 3:32 ` Stephen Rothwell
2014-03-03 5:18 ` Stephen Rothwell
2014-03-03 7:23 ` Lee Jones
2014-03-03 7:37 ` Stephen Rothwell
2014-02-11 2:25 Stephen Rothwell
2014-03-04 3:03 ` Stephen Rothwell
2014-03-04 7:05 ` Lee Jones
2014-03-04 8:06 ` Lee Jones
2014-03-04 23:36 ` 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=20140520180159.3a70193c@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=lee.jones@linaro.org \
--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).