From: Segher Boessenkool <segher@kernel.crashing.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, linux-pcmcia@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [POWERPC] 8xx: mpc885ads pcmcia support
Date: Fri, 4 May 2007 00:17:39 +0200 [thread overview]
Message-ID: <162630d74e53bc10840b667973122fff@kernel.crashing.org> (raw)
In-Reply-To: <200705032103.33809.arnd@arndb.de>
>>> For example, you could make this
>>>
>>> =A0=A0=A0=A0=A0=A0compatible =3D "8xx\0mpc885ads";
>>
>> "mpc885ads-pcmcia\0mpc8xx-pcmcia" or something like that.
>
> Right. I can never remember what goes first...
It doesn't really matter all that much; "correct"
drivers probe for the most specific thing first,
then the next most specific thing they support,
etc. It is mostly a convention.
The important thing is that you can't just call
yourself "8xx", that is way to generic a name.
Segher
WARNING: multiple messages have this Message-ID (diff)
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
linux-pcmcia@lists.infradead.org
Subject: Re: [PATCH] [POWERPC] 8xx: mpc885ads pcmcia support
Date: Fri, 4 May 2007 00:17:39 +0200 [thread overview]
Message-ID: <162630d74e53bc10840b667973122fff@kernel.crashing.org> (raw)
In-Reply-To: <200705032103.33809.arnd@arndb.de>
>>> For example, you could make this
>>>
>>> compatible = "8xx\0mpc885ads";
>>
>> "mpc885ads-pcmcia\0mpc8xx-pcmcia" or something like that.
>
> Right. I can never remember what goes first...
It doesn't really matter all that much; "correct"
drivers probe for the most specific thing first,
then the next most specific thing they support,
etc. It is mostly a convention.
The important thing is that you can't just call
yourself "8xx", that is way to generic a name.
Segher
next prev parent reply other threads:[~2007-05-03 22:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 6:54 [PATCH] [POWERPC] 8xx: mpc885ads pcmcia support Vitaly Bordug
2007-05-03 6:54 ` Vitaly Bordug
2007-05-03 7:48 ` Arnd Bergmann
2007-05-03 7:48 ` Arnd Bergmann
2007-05-03 15:43 ` Segher Boessenkool
2007-05-03 15:43 ` Segher Boessenkool
2007-05-03 19:03 ` Arnd Bergmann
2007-05-03 19:03 ` Arnd Bergmann
2007-05-03 22:17 ` Segher Boessenkool [this message]
2007-05-03 22:17 ` Segher Boessenkool
-- strict thread matches above, loose matches on Subject: below --
2007-05-03 23:57 Vitaly Bordug
2007-05-03 23:57 ` Vitaly Bordug
2007-05-04 0:01 ` Arnd Bergmann
2007-05-04 0:01 ` Arnd Bergmann
2007-05-04 19:35 ` Andrew Morton
2007-05-04 19:35 ` Andrew Morton
2007-05-05 23:27 ` Vitaly Bordug
2007-05-05 23:27 ` Vitaly Bordug
2007-05-06 0:47 Vitaly Bordug
2007-05-06 0:47 ` Vitaly Bordug
2007-05-06 1:04 ` Segher Boessenkool
2007-05-06 1:04 ` Segher Boessenkool
2007-05-06 2:04 ` David Gibson
2007-05-06 2:04 ` David Gibson
2007-05-06 9:48 ` Vitaly Bordug
2007-05-06 9:48 ` Vitaly Bordug
2007-05-06 7:44 ` Vitaly Bordug
2007-05-06 7:44 ` Vitaly Bordug
2007-05-06 13:26 ` Segher Boessenkool
2007-05-06 13:26 ` Segher Boessenkool
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=162630d74e53bc10840b667973122fff@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.