linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: linux-next: build failure after merge of the i2c tree
       [not found] ` <20160105105507.335a4fae@canb.auug.org.au>
@ 2016-01-05  1:04   ` Wolfram Sang
  0 siblings, 0 replies; only message in thread
From: Wolfram Sang @ 2016-01-05  1:04 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: linux-next, linux-kernel, Mika Westerberg, linux-i2c

[-- Attachment #1: Type: text/plain, Size: 798 bytes --]

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.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2016-01-05  1:04 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <20151216154813.2566a655@canb.auug.org.au>
     [not found] ` <20160105105507.335a4fae@canb.auug.org.au>
2016-01-05  1:04   ` linux-next: build failure after merge of the i2c tree Wolfram Sang

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).