From: "David S. Miller" <davem@redhat.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: schwidefsky@de.ibm.com, zaitcev@redhat.com,
utz.bacher@de.ibm.com, pavlic@de.ibm.com, netdev@oss.sgi.com
Subject: Re: netdevice->generate_eui64
Date: Sun, 1 Feb 2004 15:24:35 -0800 [thread overview]
Message-ID: <20040201152435.34f4231e.davem@redhat.com> (raw)
In-Reply-To: <20040130170316.789e8939.zaitcev@redhat.com>
On Fri, 30 Jan 2004 17:03:16 -0800
Pete Zaitcev <zaitcev@redhat.com> wrote:
> Does anyone know where I can find a patch to add dev->generate_eui64?
> The qeth in 2.6 tree requires it to be built (with IPv6). I am talking
> about a descendant of this patch:
> http://www.ussg.iu.edu/hypermail/linux/net/0303.0/0037.html
I don't want to see this btw, as I mentioned ipv6 specific things do not
belong in the generic device struct. There surely are better ways and I'm
totally open to suggestions.
prev parent reply other threads:[~2004-02-01 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-31 1:03 netdevice->generate_eui64 Pete Zaitcev
2004-02-01 23:24 ` David S. Miller [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=20040201152435.34f4231e.davem@redhat.com \
--to=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=pavlic@de.ibm.com \
--cc=schwidefsky@de.ibm.com \
--cc=utz.bacher@de.ibm.com \
--cc=zaitcev@redhat.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).