From: Dan Malek <dan@embeddededge.com>
To: paulus@samba.org
Cc: Troy Benjegerdes <hozer@drgw.net>,
linux-galileo@source.mvista.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: GT64260 merge warning
Date: Wed, 03 Apr 2002 21:26:29 -0500 [thread overview]
Message-ID: <3CABB9D5.7060308@embeddededge.com> (raw)
In-Reply-To: 15531.31729.263670.324103@argo.ozlabs.ibm.com
Paul Mackerras wrote:
> They can both use the same hardware address, that's perfectly legal.
Ummmm....I'm not sure arp is happy about this. Just be careful that
an arp request on one net doesn't get sent out the first interface......
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-04 2:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 5:04 GT64260 merge warning Troy Benjegerdes
2002-04-03 6:23 ` Paul Mackerras
2002-04-02 22:15 ` benh
2002-04-03 22:11 ` Paul Mackerras
2002-04-03 8:53 ` benh
2002-04-03 19:24 ` Troy Benjegerdes
2002-04-03 6:47 ` Benjamin Herrenschmidt
2002-04-03 22:02 ` Paul Mackerras
2002-04-04 2:26 ` Dan Malek [this message]
2002-04-04 7:51 ` Geert Uytterhoeven
2002-04-04 17:06 ` [Linux-galileo] " Nye Liu
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=3CABB9D5.7060308@embeddededge.com \
--to=dan@embeddededge.com \
--cc=hozer@drgw.net \
--cc=linux-galileo@source.mvista.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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).