All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kumar Gala <kumar.gala@freescale.com>
To: "Andrey Volkov" <avolkov@varma-el.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 01:10:08 -0600	[thread overview]
Message-ID: <6bac59cd11e3d6fd005b8630e67bee33@freescale.com> (raw)
In-Reply-To: <422FEFBE.4070903@varma-el.com>

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

  reply	other threads:[~2005-03-10  7:10 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 [this message]
2005-03-10  7:35               ` Andrey Volkov

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=6bac59cd11e3d6fd005b8630e67bee33@freescale.com \
    --to=kumar.gala@freescale.com \
    --cc=avolkov@varma-el.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=tnt@246tNt.com \
    /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.