Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1301214
| From | Wolfram Sang <wsa@the-dreams.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: linux-next: build failure after merge of the i2c tree |
| Date | 2016-01-05 02:10 +0100 |
| Message-ID | <qNoim-30q-3@gated-at.bofh.it> (permalink) |
| References | <qGcch-5vd-1@gated-at.bofh.it> <qNncD-1Z8-43@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
Stephen,
> > After merging the i2c tree, today's linux-next build (powerpc
> > ppc44x_defconfig) failed like this:
Oops, yes.
> > /* Bus timings (in ns) for bit-banging */
> > -static struct i2c_timings {
> > +static struct ibm_i2c_timings {
I changed it to ibm_iic_timings for consistency reasons...
> > volatile struct iic_regs __iomem *iic = dev->vaddr;
> > - const struct i2c_timings* t = &timings[dev->fast_mode ? 1 : 0];
> > + const struct ibm_i2c_timings* t = &timings[dev->fast_mode ? 1 : 0];
... and fixed the placement of the * operator ...
> > u8 mask, v, sda;
> > int i, res;
> >
> > --
> > 2.6.2
>
> Ping?
... and applied to for-next, thanks! The patch got lost because the
i2c-list was not on CC and thus patchwork couldn't catch it.
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: linux-next: build failure after merge of the i2c tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-01-05 01:00 +0100 Re: linux-next: build failure after merge of the i2c tree Wolfram Sang <wsa@the-dreams.de> - 2016-01-05 02:10 +0100
csiph-web