From: Josh Boyer <jwboyer@gmail.com>
To: "Nicolas Genevrier" <Nicolas.Genevrier@jdsu.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Ethernet breakdown on a Yosemite evaluation board
Date: Tue, 19 Feb 2008 09:21:09 -0600 [thread overview]
Message-ID: <20080219092109.551e5841@zod.rchland.ibm.com> (raw)
In-Reply-To: <8C40729B7184DC459A15060FA1AF589602045601@ENIEXCH01.ds.jdsu.net>
On Tue, 19 Feb 2008 16:04:35 +0100
"Nicolas Genevrier" <Nicolas.Genevrier@jdsu.com> wrote:
> Thanks a lot for the information,
> I apologize having not seen the posted patch.
> Everything seems to run well now.
No worries. It was a recent patch and not on this list even, so no
need to apologize. Glad things are working for you.
josh
prev parent reply other threads:[~2008-02-19 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 13:00 Ethernet breakdown on a Yosemite evaluation board Nicolas Genevrier
2008-02-19 14:17 ` Josh Boyer
2008-02-19 15:04 ` Nicolas Genevrier
2008-02-19 15:21 ` Josh Boyer [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=20080219092109.551e5841@zod.rchland.ibm.com \
--to=jwboyer@gmail.com \
--cc=Nicolas.Genevrier@jdsu.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).