linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Jiri Kosina <jkosina-AlSwsSmVLrQ@public.gmane.org>
Cc: "Richard Röjfors"
	<richard.rojfors-gfIc91nka+FZroRs9YW3xA@public.gmane.org>,
	"Ben Dooks" <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: CONFIG_I2C_XILINX doesn't complie
Date: Tue, 9 Mar 2010 08:42:29 -0800	[thread overview]
Message-ID: <20100309084229.6aa00ce8.randy.dunlap@oracle.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1003091727461.17799-ztGlSCb7Y1iN3ZZ/Hiejyg@public.gmane.org>

On Tue, 9 Mar 2010 17:31:04 +0100 (CET) Jiri Kosina wrote:

> Hi,
> 
> current Linus' tree (57d54889cd00) doesn't compile when CONFIG_I2C_XILINX 
> is enabled:
> 
> drivers/i2c/busses/i2c-xiic.c:39:28: error: linux/i2c-xiic.h: No such file or directory
> drivers/i2c/busses/i2c-xiic.c: In function ‘xiic_i2c_probe’:
> drivers/i2c/busses/i2c-xiic.c:750: error: dereferencing pointer to incomplete type
> drivers/i2c/busses/i2c-xiic.c:751: error: dereferencing pointer to incomplete type
> 
> Seems like the following commit
> 
> 	commit e1d5b6598cdc33257fe68302ae9db81d2f7bb883
> 	Author: Richard Röjfors <richard.rojfors-gfIc91nka+FZroRs9YW3xA@public.gmane.org>
> 	Date:   Thu Feb 11 10:42:00 2010 +0100
> 
> 	    i2c: Add support for Xilinx XPS IIC Bus Interface
> 
> forgot to add some header files.


http://lkml.org/lkml/2010/3/9/50http://lkml.org/lkml/2010/3/9/50

---
~Randy

      parent reply	other threads:[~2010-03-09 16:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-09 16:31 CONFIG_I2C_XILINX doesn't complie Jiri Kosina
     [not found] ` <alpine.LNX.2.00.1003091727461.17799-ztGlSCb7Y1iN3ZZ/Hiejyg@public.gmane.org>
2010-03-09 16:42   ` Randy Dunlap [this message]

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=20100309084229.6aa00ce8.randy.dunlap@oracle.com \
    --to=randy.dunlap-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
    --cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
    --cc=jkosina-AlSwsSmVLrQ@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=richard.rojfors-gfIc91nka+FZroRs9YW3xA@public.gmane.org \
    /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).