Received: by 2002:a05:6602:18e:0:0:0:0 with SMTP id m14csp7626398ioo; Fri, 3 Jun 2022 10:08:26 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxoiVY2b8Cv3OULveO07CXRCY6QEJnExtZWw3xn6UDQJFXd0tzQp2dDj6RjPBGADfLUp4l+ X-Received: by 2002:a17:906:6d05:b0:709:2c7d:5846 with SMTP id m5-20020a1709066d0500b007092c7d5846mr9943472ejr.158.1654276105978; Fri, 03 Jun 2022 10:08:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1654276105; cv=none; d=google.com; s=arc-20160816; b=gOS4cEGPLUfaq93T2vunmK+NPyeePtOg+JtsNdb4GQLOezR09dBDB1XLE/a3Anko6F mg2Hkliq/IDoogXUan+w4GygwcLSmoTM04KWb39s85WThCH+QUzlEYW94ecnf16pJoEx Z1YmXU+KJr8o2Ye2SUmr9hO18X1kBFkgKGKYmdZkcJ4feVjn/fHl9QnY2woxak2oMMum e340BlBG6WvW4WWEm7jzQJY0zx8622Dq5lQNp1XH4rgtjgBJnz5HFhDjpUKnG8K07mSf dAuCJEoVJsRZca6fm+464hrLaxAoy67rp7LSHK87caMPCpIlztwRcOOCPHcwvk7dpPO2 38zw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:to:references:message-id :content-transfer-encoding:cc:date:in-reply-to:from:subject :mime-version; bh=Fv793awA/QqkZfKyhwtdieH0eRrxEEI3r2HC4i9W60M=; b=KYh4/E6vPuUkBgDNRDAoQ82rl+3vs7EovdnV6vXNmmt/60/ugozrW2QFtXEL0U3tyg 7vcBW1aSCRnVGiq+7CTJGayAORCB+Di7hTdDjNg0nzQKjRIePodtdb0wXHojRUVNgiVG 3vxo28drwVwSk1yMepYXHtLy9PMrfjl9nwoZkoA62pqi1TovUvLuzgZgDUhyZKcs0Z2v K96abXJJlwytEyCvyoWLd32H2mkesRTvmAoc1PBQMd9XmpeoisCeUkMuBm0scnspqO2x XcMbHlhmsTEy8XDVIC7/kalB74V2Mx6fke9IhlcLrHRqJB6q7QVWr11utWShdjCbq+TP QnDQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id nc3-20020a1709071c0300b0070da0ccb401si3267566ejc.574.2022.06.03.10.07.39; Fri, 03 Jun 2022 10:08:25 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234524AbiFBP12 convert rfc822-to-8bit (ORCPT + 99 others); Thu, 2 Jun 2022 11:27:28 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46246 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229899AbiFBP12 (ORCPT ); Thu, 2 Jun 2022 11:27:28 -0400 Received: from mail.holtmann.org (coyote.holtmann.net [212.227.132.17]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 4073813C1F6 for ; Thu, 2 Jun 2022 08:27:25 -0700 (PDT) Received: from smtpclient.apple (p4ff9fc30.dip0.t-ipconnect.de [79.249.252.48]) by mail.holtmann.org (Postfix) with ESMTPSA id 2A0D2CED1A; Thu, 2 Jun 2022 17:27:24 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\)) Subject: Re: [PATCH bluetooth-next 0/3] net: 6lowpan: simplify lookup by nhc id From: Marcel Holtmann In-Reply-To: Date: Thu, 2 Jun 2022 17:27:23 +0200 Cc: Stefan Schmidt , Alexander Aring , Jukka Rissanen , "linux-bluetooth@vger.kernel.org" , linux-wpan - ML , Linus Torvalds Content-Transfer-Encoding: 8BIT Message-Id: <89A5D478-0611-4F20-B2BF-3CF3E3E82F9C@holtmann.org> References: <20220428030534.3220410-1-aahringo@redhat.com> <06164dbe-3c11-c627-0929-a399414c01bf@datenfreihafen.org> <3b5d28c4-1877-ba8f-dcb3-d5c3cbc06a1f@datenfreihafen.org> To: Luiz Augusto von Dentz X-Mailer: Apple Mail (2.3696.100.31) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org Hi Stefan, >>>>> this patch series removes the rb data structure for looking up a nhc by >>>>> nhc id. Instead we using the existing nexthdr lookup array by iterating >>>>> over it and find the right nhc by nhc id. It's simply not worth it to >>>>> use such complex handling for such small amount of nhc. As we only >>>>> support nhc ids which fits into 1 byte and there are not two byte nhc >>>>> ids values specified yet, we let the nhc layer only handle 1 byte values. >>>>> If there is the need for 2 byte nhc values we can add support for it. >>>>> >>>>> - Alex >>>>> >>>>> Alexander Aring (3): >>>>> net: 6lowpan: remove const from scalars >>>>> net: 6lowpan: use array for find nhc id >>>>> net: 6lowpan: constify lowpan_nhc structures >>>> >>>> Marcel, Luiz, are you still picking up generic 6lowpan patches or only >>>> the ones for bluetooth? >>>> >>>> These three have been around for over a month and acked by me and Jukka, >>>> but I can't find them anywhere in bluetooth-next or Linus tree. >>>> >>>> If 6lowpan is of less concern for you I can route them through my >>>> ieee80254 tree as well. >>> >>> Up to you, I was not aware they normally were merged thru >>> bluetooth-next but I would be fine merging those as well. >> >> If you and Marcel don't mind I would like to switch this over to being >> merged through ieee802154. Mostly because 6lowpan is vital for the 15.4 >> work we have. >> >> With Jukka stepping down from co-maintaining this part (thanks a lot for >> your work!) this will most likely be reviewed by Alex and me anyway. >> >> We still need to ensure that patches are hitting wpan as well as >> bluetooth mailing list, but the MAINTAINERS file handles this already. >> >> Let me know if you are unhappy with the switch. If not I will start with >> merging these three as well as the MAINTAINERS update from Jukka. > > I have no problem with that. go for it. Lets just keep the mailing list in MAINTAINERS file so we are aware of patches in this area. Regards Marcel