Hi Alex, >>> I/Simon mainly add you here in cc because this bug what Simon fixed here >>> is also inside of bluetooth 6lowpan. >> >> BTW, the v4 patch does not apply cleanly to bluetooth-next. The >> modifications were very small thou. >> > > It's a bug fix and should be go to wpan, then wpan goes to bluetooth. I > know there is some easy solveable merge conflict... but maintainers need to be > deal with it then. ;-) > > When this is an easy conflict it doesn't matter to wait on it. I hope > that's okay for all maintainers, I am new in this handling. Maintainers > isn't just "apply patches", making the right workflow and solve merge > conflicts, I think. Otherwise some maintainer will tell me "don't making merge > conflicts!", but I heard nothing something like that now. > > Or we wait when these changes are in bluetooth repo, which means also > wpan repo. since 3.17 is basically around the corner, adding it to bluetooth tree is not getting us anywhere right now. So what I would do is include it in bluetooth-next and add a CC: stable tag to it. 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
