The 'why' I want to mess with struct device in my driver is that the
alternative is to include cfg80211.h in every brc80211 source file
that does message logging, which is a form of coupling that I think is
ugly.
Why? What's wrong with that? That makes total sense.
Not in my view. Usually a driver consists of more than one layer. The
lowest layer deals with hardware and does not need to know anything
about concepts such as 'struct wiphy'. But alas, when in Rome... I will
include cfg80211.h in my lower level code.
Bye, Roland.
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
