From: Jukka Rissanen <jukka.rissanen@linux.intel.com>
To: Alexander Aring <aahringo@redhat.com>
Cc: linux-bluetooth@vger.kernel.org, linux-wpan@vger.kernel.org,
stefan@datenfreihafen.org, torvalds@linuxfoundation.org
Subject: Re: [PATCH bluetooth-next 2/3] net: 6lowpan: use array for find nhc id
Date: Tue, 03 May 2022 10:32:16 +0300 [thread overview]
Message-ID: <b058f6ec77bef1570214be4711b16012ea030d2c.camel@linux.intel.com> (raw)
In-Reply-To: <20220428030534.3220410-3-aahringo@redhat.com>
On Wed, 2022-04-27 at 23:05 -0400, Alexander Aring wrote:
> This patch will remove the complete overengineered and overthinking
> rb data
> structure for looking up the nhc by nhcid. Instead we using the
> existing
> nhc next header array and iterate over it. It works now for 1 byte
> values
> only. However there are only 1 byte nhc id values currently
> supported and IANA also does not specify large than 1 byte values
> yet.
> If there are 2 byte values for nhc ids specified we can revisit this
> data structure and add support for it.
>
> Signed-off-by: Alexander Aring <aahringo@redhat.com>
> ---
> net/6lowpan/nhc.c | 91 +++++--------------------------
> --
> net/6lowpan/nhc.h | 28 ++++------
> net/6lowpan/nhc_dest.c | 9 +---
> net/6lowpan/nhc_fragment.c | 9 +---
> net/6lowpan/nhc_ghc_ext_dest.c | 9 +---
> net/6lowpan/nhc_ghc_ext_frag.c | 11 +---
> net/6lowpan/nhc_ghc_ext_hop.c | 9 +---
> net/6lowpan/nhc_ghc_ext_route.c | 9 +---
> net/6lowpan/nhc_ghc_icmpv6.c | 9 +---
> net/6lowpan/nhc_ghc_udp.c | 9 +---
> net/6lowpan/nhc_hop.c | 9 +---
> net/6lowpan/nhc_ipv6.c | 11 +---
> net/6lowpan/nhc_mobility.c | 9 +---
> net/6lowpan/nhc_routing.c | 9 +---
> net/6lowpan/nhc_udp.c | 9 +---
> 15 files changed, 37 insertions(+), 203 deletions(-)
>
> diff --git a/net/6lowpan/nhc.c b/net/6lowpan/nhc.c
> index d6bbbd4ab38b..019f121b2449 100644
> --- a/net/6lowpan/nhc.c
> +++ b/net/6lowpan/nhc.c
> @@ -12,77 +12,26 @@
>
Acked-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
Cheers,
Jukka
next prev parent reply other threads:[~2022-05-03 7:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 3:05 [PATCH bluetooth-next 0/3] net: 6lowpan: simplify lookup by nhc id Alexander Aring
2022-04-28 3:05 ` [PATCH bluetooth-next 1/3] net: 6lowpan: remove const from scalars Alexander Aring
2022-04-28 3:47 ` net: 6lowpan: simplify lookup by nhc id bluez.test.bot
2022-05-02 19:36 ` [PATCH bluetooth-next 1/3] net: 6lowpan: remove const from scalars Stefan Schmidt
2022-05-03 7:31 ` Jukka Rissanen
2022-04-28 3:05 ` [PATCH bluetooth-next 2/3] net: 6lowpan: use array for find nhc id Alexander Aring
2022-05-02 19:37 ` Stefan Schmidt
2022-05-03 7:32 ` Jukka Rissanen [this message]
2022-04-28 3:05 ` [PATCH bluetooth-next 3/3] net: 6lowpan: constify lowpan_nhc structures Alexander Aring
2022-05-02 19:37 ` Stefan Schmidt
2022-05-03 7:32 ` Jukka Rissanen
2022-06-01 20:28 ` [PATCH bluetooth-next 0/3] net: 6lowpan: simplify lookup by nhc id Stefan Schmidt
2022-06-01 21:48 ` Luiz Augusto von Dentz
2022-06-01 21:56 ` Stefan Schmidt
2022-06-01 21:58 ` Luiz Augusto von Dentz
2022-06-02 15:27 ` Marcel Holtmann
2022-06-02 17:38 ` Stefan Schmidt
2022-06-02 17:41 ` Stefan Schmidt
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=b058f6ec77bef1570214be4711b16012ea030d2c.camel@linux.intel.com \
--to=jukka.rissanen@linux.intel.com \
--cc=aahringo@redhat.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=stefan@datenfreihafen.org \
--cc=torvalds@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.