From: Lennert Buytenhek <buytenh@wantstofly.org>
To: Daniele Orlandi <daniele@orlandi.com>
Cc: netdev@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: Request for an ARPHRD_
Date: Mon, 24 Oct 2005 23:51:40 +0200 [thread overview]
Message-ID: <20051024215140.GA10872@xi.wantstofly.org> (raw)
In-Reply-To: <200510242333.05366.daniele@orlandi.com>
On Mon, Oct 24, 2005 at 11:33:04PM +0200, Daniele Orlandi wrote:
> My main concern is that without an ARPHRD_ constant guaranteed to be
> unique I wouldn't be able to propose a patch for libpcap people to map
> the (already allocated) DLT_ to the correct ARPHRD_.
First get your code in the kernel, then submit the patch to libpcap.
--L
next prev parent reply other threads:[~2005-10-24 21:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200510240255.28416.daniele@orlandi.com>
[not found] ` <200510241807.23290.ak@suse.de>
2005-10-24 21:33 ` Request for an ARPHRD_ Daniele Orlandi
2005-10-24 21:51 ` Lennert Buytenhek [this message]
2005-10-24 22:08 ` Daniele Orlandi
2005-10-24 22:22 ` Lennert Buytenhek
2005-10-24 22:58 ` Daniele Orlandi
2005-10-24 22:24 ` Andi Kleen
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=20051024215140.GA10872@xi.wantstofly.org \
--to=buytenh@wantstofly.org \
--cc=daniele@orlandi.com \
--cc=netdev@oss.sgi.com \
--cc=netdev@vger.kernel.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).