From: axel.lin@gmail.com (Axel Lin)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-next] drivers/i2c/busses/i2c-nuc900.c build error
Date: Thu, 01 Dec 2011 20:58:24 +0800 [thread overview]
Message-ID: <1322744304.7477.1.camel@phoenix> (raw)
Hi,
I got below build error on linux-next 20111201.
CC drivers/i2c/busses/i2c-nuc900.o
drivers/i2c/busses/i2c-nuc900.c: In function 'nuc900_i2c_probe':
drivers/i2c/busses/i2c-nuc900.c:600: error: request for member 'apbfreq' in something not a structure or union
make[3]: *** [drivers/i2c/busses/i2c-nuc900.o] Error 1
make[2]: *** [drivers/i2c/busses] Error 2
make[1]: *** [drivers/i2c] Error 2
make: *** [drivers] Error 2
Regards,
Axel
WARNING: multiple messages have this Message-ID (diff)
From: Axel Lin <axel.lin@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Wan ZongShun <mcuos.com@gmail.com>,
Russell King <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.infradead.org,
Jean Delvare <khali@linux-fr.org>,
Wolfram Sang <w.sang@pengutronix.de>
Subject: [linux-next] drivers/i2c/busses/i2c-nuc900.c build error
Date: Thu, 01 Dec 2011 20:58:24 +0800 [thread overview]
Message-ID: <1322744304.7477.1.camel@phoenix> (raw)
Hi,
I got below build error on linux-next 20111201.
CC drivers/i2c/busses/i2c-nuc900.o
drivers/i2c/busses/i2c-nuc900.c: In function 'nuc900_i2c_probe':
drivers/i2c/busses/i2c-nuc900.c:600: error: request for member 'apbfreq' in something not a structure or union
make[3]: *** [drivers/i2c/busses/i2c-nuc900.o] Error 1
make[2]: *** [drivers/i2c/busses] Error 2
make[1]: *** [drivers/i2c] Error 2
make: *** [drivers] Error 2
Regards,
Axel
next reply other threads:[~2011-12-01 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 12:58 Axel Lin [this message]
2011-12-01 12:58 ` [linux-next] drivers/i2c/busses/i2c-nuc900.c build error Axel Lin
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=1322744304.7477.1.camel@phoenix \
--to=axel.lin@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.