From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Greg KH <greg@kroah.com>
Cc: Dominik Brodowski <linux@dominikbrodowski.net>,
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, 09 Mar 2005 18:21:08 +1100 [thread overview]
Message-ID: <1110352868.32525.65.camel@gaston> (raw)
In-Reply-To: <20050309060004.GE17287@kroah.com>
> > > The difficulty is that extracting and evaluating them breaks the wonderful
> > > bus-independent MODNAME implementation for hotplug suggested by Roman Kagan
> > > ( http://article.gmane.org/gmane.linux.hotplug.devel/7039 ), and that these
> > > strings may contain spaces and other "strange" characters. The latter may be
> > > worked around, but the former cannot. /etc/hotplug/pcmcia.agent looks really
> > > clean because of this MODNAME implementation:
> >
> > Same goes with Open Firmware match strings that we are about to pass
> > down to userspace as well. Hotplug will have to learn to deal with
> > those.
>
> Ok, any suggestions that don't involve hashes?
Not sure, I haven't looked at the details & issues involves (I just
"spotted" the issue about space while quick-reading lkml). I suppose
quotes around the strings are good enough, at least for OF, I yet have
to see a "compatible", "name" or "type" property with quotes in it...
Ben.
next prev parent reply other threads:[~2005-03-09 7:31 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 ` PCMCIA product id strings -> hashes generation at compilation time? [Was: Re: [patch 14/38] pcmcia: id_table for wavelan_cs] 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
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 [this message]
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=1110352868.32525.65.camel@gaston \
--to=benh@kernel.crashing.org \
--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=linux@dominikbrodowski.net \
--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