From: Lee Jones <lee.jones@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Keerthy <j-keerthy@ti.com>
Subject: Re: linux-next: build failure after merge of the mfd-lj tree
Date: Tue, 4 Mar 2014 16:06:55 +0800 [thread overview]
Message-ID: <20140304080655.GD10579@lee--X1> (raw)
In-Reply-To: <20140304140318.06e7a535ed06e9432e5df7d9@canb.auug.org.au>
> > After merging the mfd-lj tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > drivers/mfd/tps65218: struct i2c_device_id is 32 bytes. The last of 1 is:
> > 0x74 0x70 0x73 0x36 0x35 0x32 0x31 0x38 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xf0 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> > FATAL: drivers/mfd/tps65218: struct i2c_device_id is not terminated with a NULL entry!
> >
> > Caused by commit cc493e30e3a1 ("mfd: tps65218: Add driver for the
> > TPS65218 PMIC").
-rw-r--r-- 1 lee lee 6320 Mar 4 15:20 tps65218.o
Hmmm... I'm having trouble reproducing the error. My toolchain
doesn't complain about the lack of a terminating entry. I have fixed
the problem and re-pushed the branch though. Would you be kind enough
to re-test it please?
> Now that the otherproblem is fixed, I am getting this one again :-(
>
> > I have used the mfd-lj tree from next-20140210 for today.
>
> Again.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-03-04 8:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 2:25 linux-next: build failure after merge of the mfd-lj tree Stephen Rothwell
2014-03-04 3:03 ` Stephen Rothwell
2014-03-04 7:05 ` Lee Jones
2014-03-04 8:06 ` Lee Jones [this message]
2014-03-04 23:36 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
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-04-24 3:01 Stephen Rothwell
2014-05-20 8:01 Stephen Rothwell
2014-05-22 22:15 ` Linus Walleij
2014-06-19 5:20 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=20140304080655.GD10579@lee--X1 \
--to=lee.jones@linaro.org \
--cc=j-keerthy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).