Hi Alex, >>> This patch fix byteorder issues with fragment tag of generation 802.15.4 >>> 6LoWPAN fragment header. >>> >>> net/ieee802154/6lowpan_rtnl.c:278:54: warning restricted __be16 degrades to integer >>> net/ieee802154/6lowpan_rtnl.c:278:18: warning: incorrect type in assignment (different base types) >>> net/ieee802154/6lowpan_rtnl.c:278:18: expected restricted __be16 [usertype] frag_tag >>> net/ieee802154/6lowpan_rtnl.c:278:18: got unsigned short >>> >>> Signed-off-by: Alexander Aring <alex.aring@xxxxxxxxx> >>> Reported-by: Marcel Holtmann <marcel@xxxxxxxxxxxx> >>> --- >>> net/ieee802154/6lowpan_rtnl.c | 9 +++++---- >>> 1 file changed, 5 insertions(+), 4 deletions(-) >> >> patch has been applied to bluetooth-next tree. >> > > mhhh, I thought I should apply these patches to wpan-next three. That's > why it's tagged with "wpan-next" and sent to linux-wpan only. > > Just for global review and such things... > > Then I will send it with a bunch of patches to linux-bluetooth (I should > change that to send pull-requests to you). if you want to send pull requests to me that is fine as well. Right now I take patches into bluetooth-next so that they get global exposure and we get them into wireless-next on a regular basis. I am totally fine with just applying patches one by one. That is no extra work for me. I just want to get them into the tree so that they will make it into wireless-next early on. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-wpan" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
