From: Greg KH <greg@kroah.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Export symbol from I2C eeprom driver
Date: Sat, 8 Jan 2005 14:27:19 -0800 [thread overview]
Message-ID: <20050108222719.GA3226@kroah.com> (raw)
In-Reply-To: <9e473391050107220875baa32b@mail.gmail.com>
On Sat, Jan 08, 2005 at 01:08:52AM -0500, Jon Smirl wrote:
> On Fri, 7 Jan 2005 21:53:16 -0800, Greg KH <greg@kroah.com> wrote:
> > On Sat, Jan 08, 2005 at 12:34:44AM -0500, Jon Smirl wrote:
> > > Trivial patch to export a symbol from the eeprom driver. Currently
> > > there are no exported symbols. The symbol lets the radeon DRM driver
> > > link to it and modprobe will then force it to load along with the
> > > radeon driver.
> >
> > Why do you need this symbol? Or are you just saying that you need the
> > eeprom driver loaded for some reason?
> >
> > I say this as this variable is probably going to go away in the very
> > near future, as it isn't really needed at all.
>
> I just need a symbol to force eeprom to load, it can be any symbol. I
> need something for the radeon driver to link to so that modprobe will
> know to force eeprom to load when radeon is loaded. radeon is getting
> hotplug code that needs the eeprom module loaded.
Then why not try to load the module from your hotplug script?
And why do you need the eeprom driver for the radeon driver to work
properly?
thanks,
greg k-h
next prev parent reply other threads:[~2005-01-08 22:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-08 5:34 [PATCH] Export symbol from I2C eeprom driver Jon Smirl
2005-01-08 5:53 ` Greg KH
2005-01-08 6:08 ` Jon Smirl
2005-01-08 22:27 ` Greg KH [this message]
2005-01-09 0:14 ` Jon Smirl
2005-01-10 23:47 ` Greg KH
2005-01-11 2:20 ` Jon Smirl
2005-01-12 23:21 ` Greg KH
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=20050108222719.GA3226@kroah.com \
--to=greg@kroah.com \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.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