From: Adrian Bunk <bunk@fs.tum.de>
To: Corey Minyard <minyard@acm.org>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, "Davis,
Todd C" <todd.c.davis@intel.com>,
greg@kroah.com, sensors@stimpy.netroedge.com,
"Simon G. Vogl" <simon@tk.uni-linz.ac.at>
Subject: Re: 2.6.4-rc2-mm1: IPMI_SMB doesnt compile
Date: Wed, 10 Mar 2004 19:51:05 +0100 [thread overview]
Message-ID: <20040310185105.GS14833@fs.tum.de> (raw)
In-Reply-To: <404F3BC3.2090906@acm.org>
On Wed, Mar 10, 2004 at 10:01:07AM -0600, Corey Minyard wrote:
>...
> I have included a patch from Todd Davis at Intel that adds this function
> to the I2C driver. I believe Todd has been working on getting this in
> through the I2C driver writers, although the patch is fairly non-intrusive.
>
> However, I have no real way to test this patch.
>...
I can only confirm that it fixes the compilation...
The patch to i2c-core.c is strange:
> --- linux-v31/drivers/i2c/i2c-core.c 2004-02-19 19:31:07.000000000 -0600
> +++ linux/drivers/i2c/i2c-core.c 2004-03-10 09:48:08.000000000 -0600
> @@ -1256,6 +1256,12 @@
> return (func & adap_func) == func;
> }
>
> +int i2c_spin_delay;
> +void i2c_set_spin_delay(int val)
> +{
> + i2c_spin_delay = val;
> +}
> +
> EXPORT_SYMBOL(i2c_add_adapter);
> EXPORT_SYMBOL(i2c_del_adapter);
> EXPORT_SYMBOL(i2c_add_driver);
> @@ -1292,6 +1298,8 @@
>
> EXPORT_SYMBOL(i2c_get_functionality);
> EXPORT_SYMBOL(i2c_check_functionality);
> +EXPORT_SYMBOL(i2c_set_spin_delay);
> +EXPORT_SYMBOL(i2c_spin_delay);
>
> MODULE_AUTHOR("Simon G. Vogl <simon@tk.uni-linz.ac.at>");
> MODULE_DESCRIPTION("I2C-Bus main module");
>...
You can either add get/set functions and export them (more an OO
paradigm) or export the variable.
If you export the variable, it's quite useless to add such a set
function since everyone can set the variable directly.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2004-03-10 18:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 6:32 2.6.4-rc2-mm1 Andrew Morton
2004-03-08 16:20 ` 2.6.4-rc2-mm1 (compile stats) John Cherry
2004-03-13 14:26 ` Paul Dickson
2004-03-08 19:44 ` 2.6.4-rc2-mm1 Thomas Schlichter
2004-03-08 20:05 ` 2.6.4-rc2-mm1 Thomas Schlichter
2004-03-08 22:49 ` 2.6.4-rc2-mm1 Greg KH
2004-03-08 20:05 ` 2.6.4-rc2-mm1 Christian Borntraeger
2004-03-08 22:00 ` 2.6.4-rc2-mm1 Valdis.Kletnieks
2004-03-09 1:39 ` 2.6.4-rc2-mm1: IPMI_SMB doesnt compile Adrian Bunk
2004-03-10 16:01 ` Corey Minyard
2004-03-10 18:51 ` Adrian Bunk [this message]
2004-03-10 19:06 ` Greg KH
2004-03-10 20:47 ` Corey Minyard
2004-03-10 21:12 ` Greg KH
2004-03-10 19:11 ` Corey Minyard
2004-03-10 18:57 ` Greg KH
2004-03-09 4:44 ` 2.6.4-rc2-mm1 Valdis.Kletnieks
2004-03-09 20:07 ` [BUG] in generic.c, unloading alsa [Re: 2.6.4-rc2-mm1] Malte Schröder
2004-03-09 22:39 ` Andrew Morton
2004-03-10 19:50 2.6.4-rc2-mm1: IPMI_SMB doesnt compile Davis, Todd C
2004-03-10 21:20 ` Denis Vlasenko
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=20040310185105.GS14833@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=sensors@stimpy.netroedge.com \
--cc=simon@tk.uni-linz.ac.at \
--cc=todd.c.davis@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).