From: Greg KH <greg@kroah.com>
To: Mickey Stein <yekkim@pacbell.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c.h: Fix another gcc 4.0 compile failure
Date: Wed, 23 Feb 2005 09:52:51 -0800 [thread overview]
Message-ID: <20050223175251.GM13081@kroah.com> (raw)
In-Reply-To: <4218AF68.3010500@pacbell.net>
On Sun, Feb 20, 2005 at 07:40:24AM -0800, Mickey Stein wrote:
> Greg KH wrote:
>
> >On Sat, Feb 19, 2005 at 08:58:48AM -0800, Mickey Stein wrote:
> >
> >
> >>From: Mickey Stein
> >>Versions: linux-2.6.11-rc4-bk7, gcc4 (GCC) 4.0.0 20050217 (latest fc
> >>rawhide from 19Feb DL)
> >>
> >>gcc4 cvs seems to dislike "include/linux/i2c.h file":
> >>
> >>Error msg: include/linux/i2c.h:{55,194} error: array type has
> >>incomplete element type
> >>
> >>A. Daplas has recently done a workaround for this on another header
> >>file. A thread discussing this
> >>can be found by following the link below:
> >>
> >>http://gcc.gnu.org/ml/gcc/2005-02/msg00053.html
> >>
> >>The patch changes the array declaration from "struct x y[]" format to
> >>"struct x *y".
> >>I realize its only a workaround, but the gcc guys seem to be aware of
> >>this.
> >>** Note: I'm a noob at this, so feel free to make chopped liver out of
> >>this if its incorrect.
> >>patch below is also attached since I'm not sure formatting survives
> >>the cut&paste.
> >>
> >>
> >
> >The patch looks sane, but before I apply it, care to also fix up all of
> >the function pointers that are affected by this patch? Also the
> >i2c_transfer() function itself should be changed (not just the header
> >file.)
> >
> >thanks,
> >
> >greg k-h
> >
> >
> >
> Greg,
>
> I took a look for other references similar to those in my first take at
> this and found a couple more files.
> Attached is another patch that hopefully addresses the all the similar
> cases. I tried it on today's (-bk8) kernel,
> with all i2c switches enabled.
What about the i2c drivers that implement the master_xfer function? You
will now have a bunch of compiler warnings if you build them with this
patch, right?
thanks,
greg k-h
next prev parent reply other threads:[~2005-02-23 18:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-19 16:58 [PATCH] i2c.h: Fix another gcc 4.0 compile failure Mickey Stein
2005-02-19 22:37 ` Greg KH
2005-02-20 15:40 ` Mickey Stein
2005-02-23 17:52 ` Greg KH [this message]
2005-02-24 15:03 ` Corey Minyard
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=20050223175251.GM13081@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yekkim@pacbell.net \
/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