From: Andrey Volkov <avolkov@varma-el•com>
To: Kumar Gala <kumar.gala@freescale•com>
Cc: Sylvain Munaut <tnt@246tNt•com>,
paulus@samba•org, linuxppc-embedded@ozlabs•org
Subject: Re: RFC/Commit: New ocp id for CANbus devs
Date: Thu, 10 Mar 2005 10:35:50 +0300 [thread overview]
Message-ID: <422FF8D6.6060500@varma-el.com> (raw)
In-Reply-To: <6bac59cd11e3d6fd005b8630e67bee33@freescale.com>
Ok, accepted, I'll be delayed until driver will be done.
Andrey
Kumar Gala wrote:
> I would assume you plan on moving your driver over to the driver model
> which will make all of this moot.
>
> So I think Sylvain's suggestion of allocating a number for the time
> being makes the most sense until we get 52xx convert over to platform
> devices.
>
> - kumar
>
> On Mar 10, 2005, at 12:57 AM, Andrey Volkov wrote:
>
>> Sylvain Munaut wrote:
>> >
>> >> Sylvain, but what I wish now - only single number
>> >> (until driver will done).
>> >
>> > If you only need a temporary ocp ID, just fix it youself in your local
>> > tree, no need to try to push that upstream.
>>
>> I already use it as temp, but I don't want pitfalls in future (when
>> smb. take this number).
>>
>> Also, since CAN ocp present not only in MPC5200, but, AFAIK, in another
>> chips too, IMHO, it must be well known constant id.
>>
>> Regards
>> Andrey
>
>
>
prev parent reply other threads:[~2005-03-10 7:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 12:20 RFC/Commit: New ocp id for CANbus devs Andrey Volkov
2005-03-09 17:16 ` Kumar Gala
2005-03-09 17:40 ` Andrey Volkov
2005-03-09 18:37 ` Sylvain Munaut
2005-03-09 19:24 ` Kumar Gala
[not found] ` <422F486A.2080104@varma-el.com>
[not found] ` <422F534A.1020107@246tNt.com>
2005-03-10 6:57 ` Andrey Volkov
2005-03-10 7:10 ` Kumar Gala
2005-03-10 7:35 ` Andrey Volkov [this message]
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=422FF8D6.6060500@varma-el.com \
--to=avolkov@varma-el$(echo .)com \
--cc=kumar.gala@freescale$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=paulus@samba$(echo .)org \
--cc=tnt@246tNt$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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