Michal Kazior <michal.kazior@xxxxxxxxx> writes: > It was troublesome to iterate over peers and > perform sleepable calls. This will be necessary > for some upcomming changes to tx flushing. > > Make peer allocation and initial setup > protected by both ar->conf_mutex and > ar->data_lock. This way it's possible to iterate > over peers with conf_mutex and call sleepable > functions. > > Signed-off-by: Michal Kazior <michal.kazior@xxxxxxxxx> Sorry, but I'm not really getting your idea here of using both conf_mutex and data_lock to protect ar->peers. Can you elaborate more, please? Why can't we just use conf_mutex then? What am I missing? -- 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
