From: "George Spelvin" <linux@horizon.com>
To: linux@horizon.com, tj@kernel.org
Cc: akpm@linux-foundation.org, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
torvalds@linux-foundation.org
Subject: Re: [PATCH 1/2] Add lib/glob.c
Date: 11 May 2014 02:02:39 -0400 [thread overview]
Message-ID: <20140511060239.22063.qmail@ns.horizon.com> (raw)
In-Reply-To: <20140510122138.GA4721@mtj.dyndns.org>
On Sat, 10 May 2014 08:21:38 -0400, Tejun Heo wrote:
> On Fri, May 09, 2014 at 11:13:56PM -0400, George Spelvin wrote:
>> +config GLOB
>> + tristate
>> +# (Prompt disabled to reduce kbuild clutter until someone needs it.)
>> +# prompt "glob_match() function"
>> + help
>> + This option provides a glob_match function for performing simple
>> + text pattern matching. It is primarily used by the ATA code
>> + to blacklist particular drive models, but other device drivers
>> + may need similar functionality.
>> +
>> + All in-kernel drivers that require this function automatically
>> + select this option. Say N unless you are compiling an out-of
>> + tree driver which tells you it depend on it.
> Just adding glob.o to lib-y should be enough. It will be excluded
> from linking if unused.
But, I just confirmed, it will also be excluded from linking if
CONFIG_ATA=m. See for example commit b4d3ba3346f0 where some helpers
had to be moved from lib-y to obj-y to fix module load errors.
(Thanks to Randy Dunlap for this example.)
>> +#else
>> +
>> +#include <linux/module.h>
>> +#include <linux/glob.h>
>> +
>> +MODULE_DESCRIPTION("glob(7) matching");
>> +MODULE_LICENSE("Dual MIT/GPL");
> Do we make library routines separate modules usually?
There are basically three options I can see:
1) Make it non-configurable and always include the code in the kernel
using oby-y, and just accept the wasted space if CONFIG_ATA=n
2) Make it a boolean option, so CONFIG_ATA=m will force CONFIG_GLOB=y and
it will be included in the static kernel but unused until the module
is loaded.
3) Make it a tristate option, which compiles into the kernel if
CONFIG_ATA=y (the common case), and is its own module if CONFIG_ATA=m.
An awful lot of the files in lib/ take this approach.
Do you have a preference? Option 3 is the current status.
(Revised patch will come when I have the self-test converted.)
next prev parent reply other threads:[~2014-05-11 6:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140313121032.GA9981@htj.dyndns.org>
2014-05-10 3:13 ` George Spelvin
2014-05-10 3:14 ` [PATCH 2/2] libata: Use glob_match from lib/glob.c George Spelvin
2014-05-10 12:21 ` [PATCH 1/2] Add lib/glob.c Tejun Heo
2014-05-11 6:02 ` George Spelvin [this message]
2014-05-12 23:03 ` Andrew Morton
2014-05-10 12:23 ` Tejun Heo
2014-05-10 14:03 ` George Spelvin
2014-05-10 17:22 ` Randy Dunlap
2014-05-10 17:29 ` Randy Dunlap
2014-05-11 12:36 ` Tejun Heo
2014-06-07 2:44 ` [PATCH v2 1/3] " George Spelvin
2014-06-07 2:49 ` [PATCH v2 2/3] lib: glob.c: Add CONFIG_GLOB_SELFTEST George Spelvin
2014-06-11 23:04 ` Andrew Morton
2014-06-12 1:38 ` George Spelvin
2014-06-07 2:50 ` [PATCH v2 3/3] libata: Use glob_match from lib/glob.c George Spelvin
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=20140511060239.22063.qmail@ns.horizon.com \
--to=linux@horizon.com \
--cc=akpm@linux-foundation.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome