From: David Miller <davem@davemloft.net>
To: alex.aring@gmail.com
Cc: linux-wpan@vger.kernel.org, linux-bluetooth@vger.kernel.org,
netdev@vger.kernel.org, kernel@pengutronix.de,
kuznet@ms2.inr.ac.ru, jmorris@namei.org, yoshfuji@linux-ipv6.org,
kaber@trash.net
Subject: Re: [PATCH net-next] ipv6: addrconf: drop ieee802154 specific things
Date: Mon, 14 Dec 2015 16:11:04 -0500 (EST) [thread overview]
Message-ID: <20151214.161104.51809961792932420.davem@davemloft.net> (raw)
In-Reply-To: <1450122922-3174-1-git-send-email-alex.aring@gmail.com>
From: Alexander Aring <alex.aring@gmail.com>
Date: Mon, 14 Dec 2015 20:55:22 +0100
> This patch removes ARPHRD_IEEE802154 from addrconf handling. In the
> earlier days of 802.15.4 6LoWPAN, the interface type was ARPHRD_IEEE802154
> which introduced several issues, because 802.15.4 interfaces used the
> same type.
>
> Since commit 965e613d299c ("ieee802154: 6lowpan: fix ARPHRD to
> ARPHRD_6LOWPAN") we use ARPHRD_6LOWPAN for 6LoWPAN interfaces. This
> patch will remove ARPHRD_IEEE802154 which is currently deadcode, because
> ARPHRD_IEEE802154 doesn't reach the minimum 1280 MTU of IPv6.
>
> Also we use 6LoWPAN EUI64 specific defines instead using link-layer
> constanst from 802.15.4 link-layer header.
>
> Cc: David S. Miller <davem@davemloft.net>
> Cc: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
> Cc: James Morris <jmorris@namei.org>
> Cc: Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>
> Cc: Patrick McHardy <kaber@trash.net>
> Signed-off-by: Alexander Aring <alex.aring@gmail.com>
Applied, thank you.
prev parent reply other threads:[~2015-12-14 21:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 19:55 [PATCH net-next] ipv6: addrconf: drop ieee802154 specific things Alexander Aring
2015-12-14 21:11 ` David 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=20151214.161104.51809961792932420.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alex.aring@gmail.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kernel@pengutronix.de \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).