From: "David S. Miller" <davem@rth.ninka.net>
To: Solomon Peachy <solomon@linux-wlan.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] New ARPHRD types
Date: 23 Oct 2002 21:18:00 -0700 [thread overview]
Message-ID: <1035433080.9629.8.camel@rth.ninka.net> (raw)
In-Reply-To: <20021023141651.GA6644@linux-wlan.com>
On Wed, 2002-10-23 at 07:16, Solomon Peachy wrote:
> Oh, I completely agree. Unfortunately, the underlying problem is that
> the IEEE 802.11 spec has a variable-length hardware header, and that's
> not fixable, ruby slippers or no.
I'm not allowing you to put a hack special ARP header type into
the kernel when the real fix is to clean up the 802.11 handling
in the entire tree.
If that means every ethernet driver has to be aware of variable length
headers potentially, so be it.
This is the second time I'm saying this.
I'm not going to address the compression bits until you resolve this
and fix the problem properly instead of proposing hacks.
next prev parent reply other threads:[~2002-10-24 3:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 22:19 Solomon Peachy
2002-10-22 23:55 ` David S. Miller
2002-10-23 14:16 ` Solomon Peachy
2002-10-24 4:18 ` David S. Miller [this message]
2002-10-24 14:58 ` Solomon Peachy
2002-10-24 15:38 ` Alan Cox
2002-10-24 15:53 ` Solomon Peachy
2002-10-24 17:01 ` Alan Cox
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=1035433080.9629.8.camel@rth.ninka.net \
--to=davem@rth.ninka.net \
--cc=linux-kernel@vger.kernel.org \
--cc=solomon@linux-wlan.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
all inboxes | Powered by JetHome®