Arend van Spriel <arend@xxxxxxxxxxxx> writes: > Actually, the patch above should have been submitted to > wireless-drivers as it solves a suspend/hibernate issue with 4350 > device which we added in 4.4. Just to avoid any confusion you are meaning this commit: c2a43a6ba5e5 brcmfmac: Use new methods for pcie Power Management. > How should I handle that? This is what I was thinking: > > 1. submit revert for wireless-drivers-next. > 2. submit patch of c2a43a6ba5e5 for wireless-drivers. That's just messy and would prefer to avoid that. I think the best would be that you send the patch to 4.4-stable queue once the commit goes to Linus' tree during the next merge window. That way you get the fix to first 4.4.x stable releases. But not sure if it's eligible for a stable fix. BTW, I recommend sending patches to -rc release separately from the rest and marking them with intended the release number like "[PATCH 4.4]". That way it's clear for me to which tree you would like me to apply the patch. -- Kalle Valo -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
