From: Kent Yoder <key@linux.vnet.ibm.com>
To: Peter.Huewe@infineon.com
Cc: jmorris@namei.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
tpmdd-devel@lists.sourceforge.net, adlai@linux.vnet.ibm.com,
xiaoyan.zhang@intel.com, jj@chaosbits.net
Subject: Re: [GIT PULL] tpmdd: TPM drivers, tpm-rng and fixes
Date: Fri, 24 Aug 2012 10:05:33 -0500 [thread overview]
Message-ID: <20120824150533.GA2190@linux.vnet.ibm.com> (raw)
In-Reply-To: <74A44E99E3274B4CB570415926B37D440E13FD@MUCSE501.eu.infineon.com>
On Fri, Aug 24, 2012 at 08:32:47AM +0000, Peter.Huewe@infineon.com wrote:
> >> From: James Morris [mailto:jmorris@namei.org]
> >> I'm getting this error when building i2c as a module
> >> WARNING: "__i2c_transfer" [drivers/char/tpm/tpm_i2c_infineon.ko] undefined!
>
> > This is unconditionally (except I2C) available in Linus' master tree.
> > And was introduced by b37d2a3a75cb in June by Jean Delvare.
>
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b37d2a3a75cb0e72e18c29336cb2095b63dabfc8
>
> > It was tested here against Linus' tree at time of submission.
>
> Did double check it against v3.6-rc3.
> $ make ARCH=arm omap2plus_defconfig
> $ make ARCH=arm menuconfig
> -> deselected OMAP2_TYPICAL, which enables I2C to be builded as a module.
> -> selected I2C as Module.
> Build using make -> no error.
I can't reproduce this either, James, can you send out your .config?
THanks,
Kent
>
> Thanks,
> Peter
>
>
>
next prev parent reply other threads:[~2012-08-24 15:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 21:52 [GIT PULL] tpmdd: TPM drivers, tpm-rng and fixes Kent Yoder
2012-08-22 23:42 ` Jeff Garzik
2012-08-23 20:32 ` James Morris
2012-08-24 7:27 ` Peter.Huewe
2012-08-24 8:32 ` Peter.Huewe
2012-08-24 15:05 ` Kent Yoder [this message]
2012-08-24 22:02 ` James Morris
2012-08-27 7:23 ` Peter.Huewe
2012-08-27 16:17 ` Kent Yoder
2012-08-27 17:21 ` James Morris
2012-08-27 18:02 ` Kent Yoder
2012-08-27 20:28 ` James Morris
2012-08-27 21:58 ` James Morris
2012-08-27 17:19 ` James Morris
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=20120824150533.GA2190@linux.vnet.ibm.com \
--to=key@linux.vnet.ibm.com \
--cc=Peter.Huewe@infineon.com \
--cc=adlai@linux.vnet.ibm.com \
--cc=jj@chaosbits.net \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=xiaoyan.zhang@intel.com \
/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).