From: Adrian Bunk <bunk@stusta.de>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>,
Martin Michlmayr <tbm@cyrius.com>,
Al Viro <viro@ftp.linux.org.uk>, Dave Jones <davej@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Export symbols so CONFIG_INPUT works as a module
Date: Thu, 26 Jan 2006 23:17:35 +0100 [thread overview]
Message-ID: <20060126221735.GA3668@stusta.de> (raw)
In-Reply-To: <20060125075159.GC23800@suse.cz>
On Wed, Jan 25, 2006 at 08:51:59AM +0100, Vojtech Pavlik wrote:
> On Wed, Jan 25, 2006 at 12:04:06AM -0500, Dmitry Torokhov wrote:
> > On Tuesday 24 January 2006 18:14, Martin Michlmayr wrote:
> > > * Dmitry Torokhov <dmitry.torokhov@gmail.com> [2006-01-24 18:08]:
> > > > > More interesting question: is pis^H^H^Hsysfs interaction in there safe for
> > > > > modular code?
> > > >
> > > > The core should be safe, at least I was trying to make it this way, so
> > > > if you see something wrong - shout. Locking is another question
> > > > though...
> > >
> > > So do you want an updated patch using _GPL to export the symbols or to
> > > change CONFIG_INPUT to boolean?
> >
> > I guess having input core as a module does not make much sense, so
> > we should change CONFIG_INPUT to be boolean _and_ clean up the core
> > code removing module unloading support.
>
> Well, USB or SCSI cores are also modules, so I think there is some point
> in having that functionality.
>...
The difference is that USB and SCSI are not that essential, and
therefore not always enabled if CONFIG_EMBEDDED=n. It's therefore e.g.
not uncommon that distributions offer modular USB and SCSI cores.
Are there really people building kernels for that much space limited
environments that they set CONFIG_EMBEDDED=y, and at the same time want
CONFIG_INPUT=m?
I'd have expected people using CONFIG_EMBEDDED=y to usually also set
CONFIG_MODULES=n for getting a smaller kernel.
> Vojtech Pavlik
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:[~2006-01-26 22:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 18:19 [PATCH] Export symbols so CONFIG_INPUT works as a module Martin Michlmayr
2006-01-24 18:31 ` Arjan van de Ven
2006-01-24 18:34 ` Dave Jones
2006-01-24 18:41 ` Al Viro
2006-01-24 23:08 ` Dmitry Torokhov
2006-01-24 23:14 ` Martin Michlmayr
2006-01-25 5:04 ` Dmitry Torokhov
2006-01-25 7:51 ` Vojtech Pavlik
2006-01-25 10:54 ` Martin Michlmayr
2006-01-26 22:17 ` Adrian Bunk [this message]
2006-01-25 14:20 ` Jan Engelhardt
2006-02-03 22:36 ` [2.6 patch] make INPUT a bool Adrian Bunk
2006-01-24 19:08 ` [PATCH] Export symbols so CONFIG_INPUT works as a module Martin Michlmayr
2006-01-24 19:20 ` Dave Jones
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=20060126221735.GA3668@stusta.de \
--to=bunk@stusta.de \
--cc=davej@redhat.com \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tbm@cyrius.com \
--cc=viro@ftp.linux.org.uk \
--cc=vojtech@suse.cz \
/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