Grumbach, Emmanuel wrote:
> I don't see this as another datapoint. All it means is that there are ancient
> drivers that won't work at all with newer tools and that are taken into
> consideration while trying to deprecate an API.
Not just drivers, tools and applications too.
I don't think we can
Andrej Gelenberg wrote:
> i got some problems with my Qualcomm Atheros AR9485 wlan pcie card. I
> use my card as access point (with hotspotd) on amd64 machine. I use
> self compiled vanilla kernel 3.17.4 and a get a lot of
> "DMA failed to stop" messages in my kernel log. I found some reports on
>
Josh Boyer wrote:
> adds a udelay(1) call to the ath9k driver. This will cause a
> build error on various ARM configs because the value passed to udelay
> is too large:
>
> ERROR: "__bad_udelay" [drivers/net/wireless/ath/ath9k/ath9k_hw.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make:
David Miller wrote:
> John, I also don't like the ATK9K Kconfig option name change added in
> this pull request, this is exactly the kind of thing that drives
> Linus insane.
>
> Change the default, fine, but changing the name is unnecssary churn
> and adds a new config prompt that people are goin
Stephen Rothwell wrote:
> Today's linux-next merge of the wireless-next tree got a conflict in
> drivers/net/wireless/ath/ath9k/Kconfig between commit 8bb7f167a12a
> ("ath9k: Use minstrel rate control by default") from the wireless tree
> and commit cf657a2bc50d ("ath9k: Remove MAC_DEBUG") from the
Adrian Byszuk wrote:
> Aaaand failure again!
> I haven't finished bisecting yet, but as of now I have ~20 commits left:
> all related to 'mtd' - propably not a source of troubles too.
> Any other way to diagnose this bug?
I think this has been fixed by:
http://git.kernel.org/?p=linux/kernel/git/to
Larry Finger wrote:
> > I'll come up with a patch and see if kmemleak still complains.
>
> Did I miss your posting on this issue?
Nope, I haven't got to this yet, sorry. I'll try to send a patch by today.
Sujith
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the bo
Larry Finger wrote:
> My only counter argument is that none of the other paths that get to
> ath9k_htc_txcompletion_cb() leak the skb. It only happens for the path that
> goes
> through htc_connect_service().
Sure, but the TX completion handler would be invoked for every skb that is
passed
to
Larry Finger wrote:
> diff --git a/drivers/net/wireless/ath/ath9k/htc_hst.c
> b/drivers/net/wireless/ath/ath9k/htc_hst.c
> index 4a9570d..a304748 100644
> --- a/drivers/net/wireless/ath/ath9k/htc_hst.c
> +++ b/drivers/net/wireless/ath/ath9k/htc_hst.c
> @@ -278,10 +278,12 @@ int htc_connect_service
Stephen Rothwell wrote:
> Hi John,
>
> Today's linux-next merge of the wireless-next tree got a conflict in
> drivers/net/wireless/ath/ath9k/pci.c between commit 08bd108096b6 ("ath9k:
> Use PCI Express Capability accessors") from the pci tree and commit
> 046b6802c8d3 ("ath9k: Disable ASPM only fo
10 matches
Mail list logo
