public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Mahoney <jeffm@suse.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
	Olaf Hering <olh@suse.de>, Linus Torvalds <torvalds@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 2/3] openfirmware: adds sysfs nodes for	openfirmware	devices
Date: Mon, 14 Mar 2005 10:19:31 -0500	[thread overview]
Message-ID: <4235AB83.90606@suse.com> (raw)
In-Reply-To: <1110812661.5863.7.camel@gaston>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Benjamin Herrenschmidt wrote:
>>>Well, we have an unmaintained spec on one side that can't even be
>>>ordered from IEEE anymore and actual imlementations that work today,
>>>what do you chose ? ;)
>>
>>I choose the spec.  If an implementation is not conformant to the spec,
>>it doesn't "work".
>>
>>Not to say that Linux doesn't have to work around bugs in actual
>>implementations, of course.  And there's a lot of those.  Too bad ;-)
> 
> 
> Yah, well.. ok, let's say we have a spec... and an implementation that
> represents about 90% of the machines concerned. Those 90% have the
> "bug"... what do you chose ? :) 
> 
> The separator in "compatible", afaik, is \0, not space btw.
> 
> On possibiliy would be to have the kernel replace spaces with
> underscores for the sake of matching. That would make life easier for
> everybody.

I had suggested this a few days ago, but got no response. Can we agree
that this would be an acceptable solution?

- -Jeff

- --
Jeff Mahoney
SuSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCNauDLPWxlyuTD7IRAt+IAJ9mJRrrYT5trhv03qbGGPrwIwosqwCgpLS6
K/xQZE+dB4BPZc+R/FW74Nw=
=9Pgi
-----END PGP SIGNATURE-----

  reply	other threads:[~2005-03-14 15:16 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
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 [this message]
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=4235AB83.90606@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=segher@kernel.crashing.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