From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Greg KH <greg@kroah.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
jt@hpl.hp.com, linux-pcmcia@lists.infradead.org,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PCMCIA product id strings -> hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs]
Date: Wed, 9 Mar 2005 00:46:07 +0100 [thread overview]
Message-ID: <20050308234607.GA21231@isilmar.linta.de> (raw)
In-Reply-To: <20050308233706.GA11454@kroah.com>
On Tue, Mar 08, 2005 at 03:37:07PM -0800, Greg KH wrote:
> module aliases, and fixing up modprobe to handle spaces in module
> aliases wouldn't work out easier.
spaces _and_ characters. And characters are already used to separate
different fields.
pcmcia:pa"some string"pb"some other string"
doesn't look bad though, indeed. Problem is: how to access the strings in
file2alias.c? They're in different sections than the __mod_devicetables, and
you'd need to get architecture-dependant relocation... so this doesn't seem
feasible... or am I missing something?
Dominik
next prev parent reply other threads:[~2005-03-09 0:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050227161308.GO7351@dominikbrodowski.de>
[not found] ` <20050307225355.GB30371@bougret.hpl.hp.com>
[not found] ` <20050307230102.GA29779@isilmar.linta.de>
[not found] ` <20050307150957.0456dd75.akpm@osdl.org>
[not found] ` <20050307232339.GA30057@isilmar.linta.de>
2005-03-08 19:11 ` Dominik Brodowski
2005-03-08 20:34 ` Andrew Morton
2005-03-08 22:54 ` Linus Torvalds
2005-03-08 23:16 ` Dominik Brodowski
2005-03-08 23:37 ` Greg KH
2005-03-08 23:46 ` Dominik Brodowski [this message]
2005-03-08 23:39 ` Dominik Brodowski
2005-03-09 5:45 ` Benjamin Herrenschmidt
2005-03-09 6:00 ` Greg KH
2005-03-09 7:21 ` Benjamin Herrenschmidt
2005-03-09 7:19 ` Dominik Brodowski
2005-03-09 7:36 ` 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=20050308234607.GA21231@isilmar.linta.de \
--to=linux@dominikbrodowski.net \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®