From: Dan Malek <dan@embeddededge.com>
To: Vitaly Bordug <vbordug@ru.mvista.com>
Cc: linuxppc-embedded list <linuxppc-embedded@ozlabs.org>
Subject: Re: [RFC][PATCH 2.6.12-rc2 2/3] FCC Ethernet PlatformDevice support for 82xx
Date: Wed, 4 May 2005 19:08:45 -0400 [thread overview]
Message-ID: <a82c91599367bc3ffad39b98969078cd@embeddededge.com> (raw)
In-Reply-To: <4278DDAF.6010605@ru.mvista.com>
On May 4, 2005, at 10:35 AM, Vitaly Bordug wrote:
> This patch adds some helper functions to the common CPM2 code in order
> to prevent
> direct *immr usage within network driver.
No, please don't do this.
We don't need "helper" functions for the IO port in this manner.
I've got a new scheme that's been discussed, I just need a few
more "free" hours to finish it. Suffer with the current situation
for a little longer, we'll get this fixed the right way shortly.
Thanks.
-- Dan
prev parent reply other threads:[~2005-05-04 23:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 14:35 [RFC][PATCH 2.6.12-rc2 2/3] FCC Ethernet PlatformDevice support for 82xx Vitaly Bordug
2005-05-04 23:08 ` Dan Malek [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=a82c91599367bc3ffad39b98969078cd@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=vbordug@ru.mvista.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).