Hi Joe, I personally like the idea of making some kind of framework on top of printing because all ath drivers are using the same printing approach and combining all that code in one place will reduce amount of code in each particular driver. As a true engineer i like when it's less code = less work to do = less bugs:)
Suggestion is to send a patch with semicolon fix only and have a second round of convincing ath guys to change printing code. How does that sound? On Wed, Nov 6, 2013 at 5:55 PM, Joe Perches <j...@perches.com> wrote: > On Wed, 2013-11-06 at 07:49 +0000, Eugene Krasnikov wrote: >> Hm... when it comes to semicolon the patch seems to be good. When it >> comes to dynamic debugging i think we should have a separate >> discussion about that. >> I personally like the whole idea about dynamic debug but if you want >> to change it i would suggest to have some kind of framework for all >> ath drivers(or maybe all wireless drivers). Because obviously you can >> find common code in every driver that defines it's own debug >> functions/debug levels and so on. Why not to make a framework with >> standard API/levels? > > You need to bring that up with the Atheros folk. > I've tried. The view seemed to be it was more > trouble than it was worth. > > > -- Best regards, Eugene _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
