From: Greg KH <greg@kroah.com>
To: Corey Minyard <minyard@acm.org>
Cc: Adrian Bunk <bunk@fs.tum.de>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, "Davis,
Todd C" <todd.c.davis@intel.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 13:12:38 -0800 [thread overview]
Message-ID: <20040310211238.GB21966@kroah.com> (raw)
In-Reply-To: <404F7EF8.5020402@acm.org>
On Wed, Mar 10, 2004 at 02:47:52PM -0600, Corey Minyard wrote:
> Greg KH wrote:
>
> >On Wed, Mar 10, 2004 at 07:51:05PM +0100, Adrian Bunk wrote:
> >
> >
> >>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:
> >>
> >>
> >
> >And dumb, and incorrect :(
> >
> >
> >
> Wrong as in: "This code will not work" or wrong as in: "don't export the
> variable and the function", or both?
Wrong as in "don't export the variable, the function, and on top of
that, not document what you are trying to do."
> I certainly agree that exporting both is wrong, there should really be
> two inline functions with only the variable exported, or only
> functions exported and the variable hidden. That's an easy change.
>
> However, if the code does not work, that is a bigger deal. I'm fairly
> sure it works in some cases, but not sure about all.
>
> The patch I posted is for 2.6, BTW.
But you never sent it to the i2c maintainers, right?
I understand what you are trying to accomplish with this type of patch,
but if you _really_ need to make this kind of change, please change the
name to something that really stands out as being not the thing you ever
would want to do.
Something like:
i2c_we_just_paniced_and_can_not_sleep_anymore()
thanks,
greg k-h
next prev parent reply other threads:[~2004-03-10 21:15 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
2004-03-10 19:06 ` Greg KH
2004-03-10 20:47 ` Corey Minyard
2004-03-10 21:12 ` Greg KH [this message]
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=20040310211238.GB21966@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=bunk@fs.tum.de \
--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
all inboxes | Powered by JetHome®