which chip ? And what's the GPIO number ? Thanks, Miaoqing ________________________________________ From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx> Sent: Tuesday, May 31, 2016 3:35 PM To: Kalle Valo Cc: Stephen Rothwell; ath9k-devel; linux-next@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; linux-wireless@xxxxxxxxxxxxxxx; ath9k-devel@xxxxxxxxxxxxxxx; netdev@xxxxxxxxxxxxxxx; Miaoqing Pan Subject: Re: ath9k gpio request On Tuesday 31 May 2016 01:01 PM, Kalle Valo wrote: > (Changing subject to a more descriptive one, was "Re: linux-next: Tree > for May 30") > > Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx> writes: > >> Hi All, >> I have just built and booted with next-20160530 and my dmesg is full >> of warnings from ath9k. Last kernel tested was v4.6 and there was no >> problem with that. >> <snip> > The traces look incomplete to me, is there anything more before the > "Call Trace:" line? Full unedited logs are usually the best. sure, its attached. those two warnings are recursively going on and there is nothing else left in dmesg to see what started it. Regards Sudip -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
