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
