From: Jeff Mahoney <jeffm@suse.com>
To: Olaf Hering <olh@suse.de>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] openfirmware: adds sysfs nodes for openfirmware devices
Date: Fri, 04 Mar 2005 11:35:10 -0500 [thread overview]
Message-ID: <42288E3E.5090208@suse.com> (raw)
In-Reply-To: <20050304110215.GC14408@suse.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Olaf Hering wrote:
> On Thu, Mar 03, Jeff Mahoney wrote:
>
>
>>-----BEGIN PGP SIGNED MESSAGE-----
>>Hash: SHA1
>>
>>Olaf Hering wrote:
>>
>>> On Thu, Mar 03, Jeff Mahoney wrote:
>>>
>>>
>>>
>>>>Is whitespace (in any form) allowed in the compatible value?
>>>
>>>
>>>Yes, whitespace is used at least in the toplevel compatible file, like
>>>'Power Macintosh' in some Pismo models.
>>>
>>
>>Oh well, it was wishful thinking anyway. ;)
>
>
> The same thing needs to be solved for vio devices, the properties can
> contain spaces. depmod and modprobe have to deal with it to generate a
> valid module.alias file.
The solution I ended up going with was the original CRLF suggestion, and
then I pass around a group of environment vars in userspace rather than
a single line. This works as before, but works with commas and isn't as
ugly as I had thought it might be.
As far as the modules.aliases file goes, I'm not sure what our options
are there. Is the only requirement that the aliases be consistent in the
kernel and in userspace? Since aliases for OF devices haven't previously
existed, I defined the format. Is there any reason I couldn't define the
format such that whitepsace is replaced by underscores, thus eliminating
this issue?
- -Jeff
- --
Jeff Mahoney
SuSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFCKI4+LPWxlyuTD7IRAvNOAJ0aopD1JcpUpoAMeuI1EVSBVbICCQCgmHVN
QKswIpQ//5SxjnXIk02PBts=
=K/kB
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-03-04 16:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 21:18 [PATCH 2/3] openfirmware: adds sysfs nodes for openfirmware devices Jeffrey Mahoney
2005-03-02 23:32 ` Benjamin Herrenschmidt
2005-03-03 18:19 ` Jeff Mahoney
2005-03-03 20:23 ` Olaf Hering
2005-03-03 21:17 ` Jeff Mahoney
2005-03-04 11:02 ` Olaf Hering
2005-03-04 16:35 ` Jeff Mahoney [this message]
2005-03-13 15:17 ` Segher Boessenkool
2005-03-14 14:03 ` Benjamin Herrenschmidt
2005-03-14 14:06 ` Olaf Hering
2005-03-14 14:27 ` Segher Boessenkool
2005-03-14 15:04 ` Benjamin Herrenschmidt
2005-03-14 15:19 ` Jeff Mahoney
2005-03-14 15:19 ` Segher Boessenkool
2005-03-14 21:47 ` Benjamin Herrenschmidt
2005-03-03 22:52 ` Benjamin Herrenschmidt
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=42288E3E.5090208@suse.com \
--to=jeffm@suse.com \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olh@suse.de \
--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