From: Vitaly Bordug <vbordug@ru•mvista.com>
To: Kumar Gala <galak@freescale•com>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs•org>
Subject: Re: RFC: cpm2_devices.c
Date: Wed, 15 Jun 2005 11:55:42 +0400 [thread overview]
Message-ID: <42AFDEFE.2040508@ru.mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0506142231040.2447@nylon.am.freescale.net>
Kumar,
I assume this as a IMMR enumerating you promised to help with. Is it in
the final state? And what was the reason of fcc_regs_c removal?
I'm also going to change the files name to cpm2_.. .
Allen,
I'll provide a patch containing these platform stuff together with
platform-specific device structures which is utilized in the fs_enet
driver. As now it's clear that fcc_mem dpram offset should be passed
over platform_info, these structures at least regarding fs_enet probably
will not change.
--
Sincerely, Vitaly
next prev parent reply other threads:[~2005-06-15 7:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-14 18:18 RFC: cpm2_devices.c Allen Curtis
2005-06-15 3:35 ` Kumar Gala
2005-06-15 3:57 ` Allen Curtis
2005-06-15 4:13 ` Kumar Gala
2005-06-15 4:41 ` Allen Curtis
2005-06-15 14:24 ` Jason McMullan
2005-06-15 15:06 ` Kumar Gala
2005-06-15 17:48 ` Allen Curtis
2005-06-15 18:05 ` Vitaly Bordug
2005-06-15 14:29 ` Kumar Gala
2005-06-15 14:30 ` Kumar Gala
2005-06-16 15:12 ` Dan Malek
2005-06-16 15:33 ` Kumar Gala
2005-06-16 15:42 ` Allen Curtis
2005-06-16 15:53 ` Kumar Gala
2005-06-16 16:39 ` Allen Curtis
2005-06-16 19:33 ` Dan Malek
2005-06-15 7:55 ` Vitaly Bordug [this message]
2005-06-15 14:25 ` Kumar Gala
2005-06-15 14:33 ` Jason McMullan
2005-06-15 15:01 ` Kumar Gala
2005-06-15 15:31 ` Vitaly Bordug
2005-06-15 15:41 ` Kumar Gala
2005-06-15 16:07 ` Vitaly Bordug
2005-06-16 6:42 ` Pantelis Antoniou
2005-06-16 9:33 ` Wolfgang Denk
2005-06-16 15:02 ` Kumar Gala
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=42AFDEFE.2040508@ru.mvista.com \
--to=vbordug@ru$(echo .)mvista.com \
--cc=galak@freescale$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/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