mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: 22 Oct 2002 16:55:36 -0700	[thread overview]
Message-ID: <1035330936.16084.23.camel@rth.ninka.net> (raw)
In-Reply-To: <20021021221936.GA32390@linux-wlan.com>

On Mon, 2002-10-21 at 15:19, Solomon Peachy wrote:
> IEEE 802.11 has a variable "hardware" header length, 24 bytes for most
> frames but 30 bytes for others.  This poses a problem if you want to
> expose a native 802.11 netdev interface to the OS, as  
> netdev->hardhdr_len et.al. aren't variable.
> 
> But wait, isn't there already ARPHRD_IEEE80211? Yes, but unfortunately,

If ARPHRD_IEEE80211 assumes 24 bytes, and like you say it shouldn't,
fix that bug instead.  Don't add new ARP header types just to put
a bandaid on another bug.



  reply	other threads:[~2002-10-22 23:38 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 [this message]
2002-10-23 14:16   ` Solomon Peachy
2002-10-24  4:18     ` David S. Miller
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=1035330936.16084.23.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®