<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/net/rfkill/rfkill.c, branch v2.6.24</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v2.6.24</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v2.6.24'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2008-01-21T04:31:36Z</updated>
<entry>
<title>rfkill: call rfkill_led_trigger_unregister() on error</title>
<updated>2008-01-21T04:31:36Z</updated>
<author>
<name>Eric Paris</name>
<email>eparis@redhat.com</email>
</author>
<published>2008-01-13T21:20:56Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=632041f306707df94110441f55b1458ebeb096db'/>
<id>urn:sha1:632041f306707df94110441f55b1458ebeb096db</id>
<content type='text'>
Code inspection turned up that error cases in rfkill_register() do not
call rfkill_led_trigger_unregister() even though we have already
registered.

Signed-off-by: Eric Paris &lt;eparis@redhat.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>rfkill: fix double-mutex-locking</title>
<updated>2007-11-29T23:08:48Z</updated>
<author>
<name>Michael Buesch</name>
<email>mb@bu3sch.de</email>
</author>
<published>2007-11-28T16:49:34Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=7f4c534178722ac9ffb4feae3a4d54e3fbe3f22c'/>
<id>urn:sha1:7f4c534178722ac9ffb4feae3a4d54e3fbe3f22c</id>
<content type='text'>
rfkill_toggle_radio is called from functions where
rfkill-&gt;mutex is already aquired.

Remove the lock from rfkill_toggle_radio() and add it to
the only calling function that calls it without the lock held.

Signed-off-by: Michael Buesch &lt;mb@bu3sch.de&gt;
Acked-by: Ivo van Doorn &lt;IvDoorn@gmail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>rfkill: Fix sparse warning</title>
<updated>2007-11-11T06:00:28Z</updated>
<author>
<name>Michael Buesch</name>
<email>mb@bu3sch.de</email>
</author>
<published>2007-11-02T19:18:11Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=2736622344e9af9801392edf9e733e8a8f6931d1'/>
<id>urn:sha1:2736622344e9af9801392edf9e733e8a8f6931d1</id>
<content type='text'>
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>rfkill: Use mutex_lock() at register and add sanity check</title>
<updated>2007-11-11T06:00:15Z</updated>
<author>
<name>Michael Buesch</name>
<email>mb@bu3sch.de</email>
</author>
<published>2007-10-28T14:16:50Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=7319f1e6bcf04abd2eddb19747b0933a76f839ce'/>
<id>urn:sha1:7319f1e6bcf04abd2eddb19747b0933a76f839ce</id>
<content type='text'>
Replace mutex_lock_interruptible() by mutex_lock() in rfkill_register(),
as interruptible doesn't make sense there.

Add a sanity check for rfkill-&gt;type, as that's used for an unchecked dereference
in an array and might cause hard to debug crashes if the driver sets this
to an invalid value.

Signed-off-by: Michael Buesch &lt;mb@bu3sch.de&gt;
Signed-off-by: Ivo van Doorn &lt;IvDoorn@gmail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>rfkill: Use subsys_initcall</title>
<updated>2007-11-11T05:59:33Z</updated>
<author>
<name>Michael Buesch</name>
<email>mb@bu3sch.de</email>
</author>
<published>2007-10-28T13:39:02Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=2bf236d55e5ea2b92ed5235af09997c2995b316b'/>
<id>urn:sha1:2bf236d55e5ea2b92ed5235af09997c2995b316b</id>
<content type='text'>
We must use subsys_initcall, because we must initialize before a
driver calls rfkill_register().

Signed-off-by: Michael Buesch &lt;mb@bu3sch.de&gt;
Signed-off-by: Ivo van Doorn &lt;IvDoorn@gmail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>rfkill: Register LED triggers before registering switch</title>
<updated>2007-11-11T05:59:11Z</updated>
<author>
<name>Michael Buesch</name>
<email>mb@bu3sch.de</email>
</author>
<published>2007-10-28T12:07:54Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=8a8f1c0437a77cce29c1cb6089f01f22a6d9ca6e'/>
<id>urn:sha1:8a8f1c0437a77cce29c1cb6089f01f22a6d9ca6e</id>
<content type='text'>
Registering the switch triggers a LED event, so we must register
LED triggers before the switch.
This has a potential to fix a crash, depending on how the device
driver initializes the rfkill data structure.

Signed-off-by: Michael Buesch &lt;mb@bu3sch.de&gt;
Signed-off-by: Ivo van Doorn &lt;IvDoorn@gmail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>[RFKILL]: Add support for hardware-only rfkill buttons</title>
<updated>2007-10-10T23:54:11Z</updated>
<author>
<name>Michael Buesch</name>
<email>mb@bu3sch.de</email>
</author>
<published>2007-09-27T19:34:23Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=20405c08412a4d89357870d7220f9fb1c458b286'/>
<id>urn:sha1:20405c08412a4d89357870d7220f9fb1c458b286</id>
<content type='text'>
Buttons that work directly on hardware cannot support
the "user_claim" functionality. Add a flag to signal
this and return -EOPNOTSUPP in this case.
b43 is such a device.

Signed-off-by: Michael Buesch &lt;mb@bu3sch.de&gt;
Acked-by: Ivo van Doorn &lt;IvDoorn@gmail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>[RFKILL]: Add support for an rfkill LED.</title>
<updated>2007-10-10T23:54:10Z</updated>
<author>
<name>Michael Buesch</name>
<email>mb@bu3sch.de</email>
</author>
<published>2007-09-27T19:33:12Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=135900c182c321a4888ec496b014e6707272faca'/>
<id>urn:sha1:135900c182c321a4888ec496b014e6707272faca</id>
<content type='text'>
This adds a LED trigger.

Signed-off-by: Michael Buesch &lt;mb@bu3sch.de&gt;
Acked-by: Ivo van Doorn &lt;IvDoorn@gmail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>[RFKILL]: Move rfkill_switch_all out of global header</title>
<updated>2007-10-10T23:53:29Z</updated>
<author>
<name>Ivo van Doorn</name>
<email>IvDoorn@gmail.com</email>
</author>
<published>2007-09-27T21:57:05Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=fe242cfd3390b1c7d54d60f7ebb6a4054804cd41'/>
<id>urn:sha1:fe242cfd3390b1c7d54d60f7ebb6a4054804cd41</id>
<content type='text'>
rfkill_switch_all shouldn't be called by drivers directly,
instead they should send a signal over the input device.

To prevent confusion for driver developers, move the
function into a rfkill private header.

Signed-off-by: Ivo van Doorn &lt;IvDoorn@gmail.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>[RFKILL]: Add support for ultrawideband</title>
<updated>2007-10-10T23:49:23Z</updated>
<author>
<name>Ivo van Doorn</name>
<email>IvDoorn@gmail.com</email>
</author>
<published>2007-09-13T07:21:31Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=e0665486b78b8efb9c25019ad29b4a4c9c1e9dfc'/>
<id>urn:sha1:e0665486b78b8efb9c25019ad29b4a4c9c1e9dfc</id>
<content type='text'>
This patch will add support for UWB keys to rfkill,
support for this has been requested by Inaky.

Signed-off-by: Ivo van Doorn &lt;IvDoorn@gmail.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
</feed>
