From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Liam Girdwood <lrg@slimlogic•co.uk>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Anuj Aggarwal <anuj.aggarwal@ti•com>
Subject: linux-next: voltage tree build failure
Date: Mon, 24 Aug 2009 14:40:44 +1000 [thread overview]
Message-ID: <20090824144044.fad8639f.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
Hi Liam,
Today's linux-next build (x86_64 allmodconfig) failed like this:
drivers/regulator/tps65023-regulator: struct i2c_device_id is 32 bytes. The last of 1 is:
0x74 0x70 0x73 0x36 0x35 0x30 0x32 0x33 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
FATAL: drivers/regulator/tps65023-regulator: struct i2c_device_id is not terminated with a NULL entry!
Caused by commit 9cfd343f14bf4bd95f8bfc6a1d411d2002bf94d8 ("Regulator:
Add TPS65023 regulator driver").
I have used the version of the voltage tree from next-20090821 for today.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-08-24 4:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 4:40 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-12 2:26 linux-next: voltage tree build failure Stephen Rothwell
2009-10-12 2:50 ` Haojian Zhuang
2009-10-12 12:57 ` Mark Brown
2009-10-12 13:35 ` Samuel Ortiz
2009-04-28 6:24 Stephen Rothwell
2009-04-28 11:08 ` Liam Girdwood
2009-04-28 11:42 ` Stephen Rothwell
2009-04-30 11:06 ` Mike Rapoport
2009-01-21 2:46 Stephen Rothwell
2009-01-21 14:04 ` Jonathan Cameron
2008-07-14 13:35 Stephen Rothwell
2008-07-14 13:48 ` Liam Girdwood
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=20090824144044.fad8639f.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=anuj.aggarwal@ti$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lrg@slimlogic$(echo .)co.uk \
/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