linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Bordug <vitb@kernel.crashing.org>
To: "Bizhan Gholikhamseh (bgholikh)" <bgholikh@cisco.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Where is fcc_enet.c
Date: Mon, 11 Feb 2008 12:37:03 +0300	[thread overview]
Message-ID: <20080211123703.5e046897@kernel.crashing.org> (raw)
In-Reply-To: <F795765B112E7344AF36AA911279641502D1AA74@xmb-sjc-212.amer.cisco.com>

On Sun, 10 Feb 2008 15:08:46 -0800
Bizhan Gholikhamseh (bgholikh) wrote:

> Hi,
> I am porting to Linux 2.6.24 from linux 2.6.11 on mpc85xx cds
> platform, I am not able to locate fcc_enet.c file under
> linux 2.6.24 source tree, any idea????
try drivers/net/fs_enet

at least CPM2 FCC is handled in there.


-- 
Sincerely, Vitaly

      reply	other threads:[~2008-02-11  9:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-10 23:08 Where is fcc_enet.c Bizhan Gholikhamseh (bgholikh)
2008-02-11  9:37 ` Vitaly Bordug [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=20080211123703.5e046897@kernel.crashing.org \
    --to=vitb@kernel.crashing.org \
    --cc=bgholikh@cisco.com \
    --cc=linuxppc-embedded@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 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).