On Thu, 2011-04-21 at 18:16 +0530, Yogesh Ashok Powar wrote: > I thought about this initially, but then realized that this will not > handle the scenario where we disable the key which needs tailroom space > reservation? Once the last key, that needs tailroom reservation, is > disabled, we can skip the tailroom code again? Well, it kinda goes like this: key added -> need tailroom code key put into HW -> no longer need tailroom code key removed from HW -> need tailroom code again key deleted -> no longer need tailroom code johannes -- 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
