On ti, 2014-09-23 at 12:33 +0200, Alexander Aring wrote: > On Tue, Sep 23, 2014 at 01:14:06PM +0300, Jukka Rissanen wrote: > > Hi Alex, > > > > On ti, 2014-09-23 at 11:35 +0200, Alexander Aring wrote: > > > Jukka, > > > > > > 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. Actually, the v4 patch only touches net/ieee802154/6lowpan_rtnl.c which is not used by bluetooth so no worries here. Cheers, Jukka -- 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
