Re: [PATCH] Add a new PID/VID 0cf3/e005 for AR3012.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am 09.07.2014 13:05, schrieb Marcel Holtmann:
Hi Alexander,

which is wrong and disables the ath3k driver.

I reverted the broken patch in bluetooth.git now and marked it for
3.15 stable.

Must got missed, it's not in 3.15.4 nor in 3.15.5.

As my solution was a revert too, I can offer a Tested-By, if such is
needed, at least in regard to the point that ath3k-dongles will work
again after reverting ca58e5.

it is in net tree, but not in 3.16-rcX yet. Only after it got into
Linus' tree it can be backported to stable tree.

Ah, the funny maze of linux kernel repos. ;)

That lead me to the idea to rename bluetooth-next to bluetooth-ubernext because that what be more appropriate if bluetooth-next ends up in net-next or linux-next or something-else-next. ;)

it goes bluetooth-next -> linux-next
	  `- wireless-next -> net-next -> linux

Oh, so ubernext would be an understatement.

That makes up for some interesting stats about timing.

If I assume every one of those next repos do use just a 2 week testing period before forwarding patches, I end up with 2 + 2 + 2 + 2 weeks.

And if every one of these trees do use one month, this would be 4 month until a patch ends up in mainline where it resides another 3 month until it reaches people.

Regards,

Alexander Holler
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux