Re: [PATCH] staging: brcm80211: implementation of RFKILL functionality

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

 



On Wed, 09 Mar 2011 22:31:53 +0100, Greg KH <gregkh@xxxxxxx> wrote:

Wait, why would this go to the -stable tree?  Does it fix a real
problem, as described it only looks like you are adding new
functionality to the driver, which is not allowed in -stable releases.
Hi Greg,

That was indeed the reason why this was initially posting to staging-next only. However, users of the driver have been using the rf button and found it freezing up their system (see our email exchange title "brcm80211: the system freezes if booted with laptop wifi switch to OFF"). You could argue that they should read the TODO/README/wireless twiki and not touch the RF button when using this driver.

From the thread I concluded you were ok with these changes going into linus tree. We are still good at confusing each other ;-) It turned out that the patch also still contained my debug printk code so probably best to ignore the patch. Let me know whether you will accept a corrected patch for this or leave it.

Gr. AvS
--
"The most merciful thing in the world, I think, is the inability of the human
mind to correlate all its contents." - "The Call of Cthulhu"

_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel


[Index of Archives]     [Linux Driver Backports]     [DMA Engine]     [Linux GPIO]     [Linux SPI]     [Video for Linux]     [Linux USB Devel]     [Linux Coverity]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux