Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: linux-wpan@vger.kernel.org
Subject: Re: [PATCH 4/8] ieee802154: Remove 802.15.4/6LoWPAN checks for interface MTU.
Date: Wed, 20 May 2015 12:45:24 +0200	[thread overview]
Message-ID: <20150520104524.GI3978@omega> (raw)
In-Reply-To: <20150519195007.GP11014@wantstofly.org>

On Tue, May 19, 2015 at 10:50:07PM +0300, Lennert Buytenhek wrote:
> In the past, 802.15.4 interfaces and 6LoWPAN interfaces used the
> same dev->type (ARPHRD_IEEE802154), and 802.15.4 interfaces were
> distinguished from 6LoWPAN interfaces by their differing dev->mtu.
> 
> 6LoWPAN interfaces have their own ARPHRD type now, so there is no
> longer any need to check dev->mtu to distinguish 802.15.4 devices
> from 6LoWPAN devices.
> 
> Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>

Acked-by: Alexander Aring <alex.aring@gmail.com>

btw: the reason why I introduced this was that I had really fear to
change the lowpan ARPHRD, because there exists already a huge of
software which support this and somebody told me that when he delete a
lowpan interface with the iz tool then the whole kernel was crashed.
This was indeed true because it had freed some resources which was
allocated on a wpan interface only.

But we don't need this anymore, yes. I changed the ARPHRD and nobody
screamed that his/her software doesn't work anymore.

- Alex

  reply	other threads:[~2015-05-20 10:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1432064518.git.buytenh@wantstofly.org>
2015-05-19 19:49 ` [PATCH 1/8] ieee802154 socket: Return EMSGSIZE from raw_sendmsg() if packet too big Lennert Buytenhek
2015-05-20 10:36   ` Alexander Aring
2015-05-19 19:50 ` [PATCH 2/8] Documentation/networking/ieee802154.txt: fix various inaccuracies Lennert Buytenhek
2015-05-19 22:05   ` Marcel Holtmann
2015-05-20  8:36     ` Lennert Buytenhek
2015-05-20  8:40       ` Stefan Schmidt
2015-05-20  8:54       ` Alexander Aring
2015-05-20  9:14         ` Lennert Buytenhek
2015-05-20  9:54       ` Marcel Holtmann
2015-05-20  8:36     ` Stefan Schmidt
2015-05-19 19:50 ` [PATCH 3/8] ieee802154: Remove ieee802154_reduced_mlme_ops references Lennert Buytenhek
2015-05-20 10:34   ` Alexander Aring
2015-05-19 19:50 ` [PATCH 4/8] ieee802154: Remove 802.15.4/6LoWPAN checks for interface MTU Lennert Buytenhek
2015-05-20 10:45   ` Alexander Aring [this message]
2015-05-19 19:50 ` [PATCH 5/8] ieee802154 6lowpan: Don't implement ieee802154_mlme_ops Lennert Buytenhek
2015-05-20 10:41   ` Alexander Aring
2015-05-25  6:17     ` Lennert Buytenhek
2015-05-19 19:50 ` [PATCH 6/8] ieee802154 socket: No need to check for ARPHRD_IEEE802154 in raw_bind() Lennert Buytenhek
2015-05-20 10:42   ` Alexander Aring
2015-05-19 19:50 ` [PATCH 7/8] mac802154: mac802154_header_create() optimisation Lennert Buytenhek
2015-05-20 10:33   ` Alexander Aring
2015-05-19 19:50 ` [PATCH 8/8] mac802154: mac802154_mlme_start_req() optimisation Lennert Buytenhek
2015-05-20 10:11   ` Alexander Aring

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=20150520104524.GI3978@omega \
    --to=alex.aring@gmail.com \
    --cc=buytenh@wantstofly.org \
    --cc=linux-wpan@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