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, "Zhu,
Lejun" <lejun.zhu@linux•intel.com>,
"Yang, Bin" <bin.yang@intel•com>,
Mika Westerberg <mika.westerberg@linux•intel.com>,
Alexandre Courbot <acourbot@nvidia•com>,
Linus Walleij <linus.walleij@linaro•org>
Subject: linux-next: build failure after merge of the mfd-lj tree
Date: Thu, 19 Jun 2014 15:20:13 +1000 [thread overview]
Message-ID: <20140619152013.7792c616@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 591 bytes --]
Hi Lee,
After merging the mfd-lj tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/gpio/gpio-crystalcove.c: In function 'crystalcove_gpio_dbg_show':
drivers/gpio/gpio-crystalcove.c:286:3: error: implicit declaration of function 'seq_printf' [-Werror=implicit-function-declaration]
seq_printf(s, " gpio-%-2d %s %s %s %s ctlo=%2x,%s %s %s\n",
^
Caused by commit 104fb1d5153c ("gpio: Add support for Intel Crystal
Cove PMIC").
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2014-06-19 5:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 5:20 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-20 8:01 linux-next: build failure after merge of the mfd-lj tree Stephen Rothwell
2014-05-22 22:15 ` Linus Walleij
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=20140619152013.7792c616@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=acourbot@nvidia$(echo .)com \
--cc=bin.yang@intel$(echo .)com \
--cc=lee.jones@linaro$(echo .)org \
--cc=lejun.zhu@linux$(echo .)intel.com \
--cc=linus.walleij@linaro$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mika.westerberg@linux$(echo .)intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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