01 Nov, 2011

1 commit

• d9b938421   net: add moduleparam.h for users of module_param/MODULE_PARM_DESC ... Browse Code »

  These files were getting access to these two via the implicit
  presence of module.h everywhere. They aren't modules, so they
  don't need the full module.h inclusion though.

  Signed-off-by: Paul Gortmaker

  Paul Gortmaker

  2011-11-01 07:30:29 +0800  

24 Sep, 2010

1 commit

• a02cec215   net: return operator cleanup ... Browse Code »

  Change "return (EXPR);" to "return EXPR;"

  return is not a function, parentheses are not required.

  Signed-off-by: Eric Dumazet
  Signed-off-by: David S. Miller

  Eric Dumazet

  2010-09-24 05:33:39 +0800  

03 Mar, 2010

1 commit

• 3082a2b7b   rfkill: Add support for KEY_RFKILL ... Browse Code »

  Add support for handling KEY_RFKILL in the rfkill input module. This
  simply toggles the state of all rfkill devices. The comment in rfkill.h
  is also updated to reflect that RFKILL_TYPE_ALL may be used inside the
  kernel.

  Signed-off-by: Matthew Garrett
  Acked-by: Marcel Holtmann
  Signed-off-by: John W. Linville

  Matthew Garrett

  2010-03-03 03:28:49 +0800  

04 Jun, 2009

1 commit

• 19d337dff   rfkill: rewrite ... Browse Code »

  This patch completely rewrites the rfkill core to address
  the following deficiencies:

  * all rfkill drivers need to implement polling where necessary
  rather than having one central implementation

  * updating the rfkill state cannot be done from arbitrary
  contexts, forcing drivers to use schedule_work and requiring
  lots of code

  * rfkill drivers need to keep track of soft/hard blocked
  internally -- the core should do this

  * the rfkill API has many unexpected quirks, for example being
  asymmetric wrt. alloc/free and register/unregister

  * rfkill can call back into a driver from within a function the
  driver called -- this is prone to deadlocks and generally
  should be avoided

  * rfkill-input pointlessly is a separate module

  * drivers need to #ifdef rfkill functions (unless they want to
  depend on or select RFKILL) -- rfkill should provide inlines
  that do nothing if it isn't compiled in

  * the rfkill structure is not opaque -- drivers need to initialise
  it correctly (lots of sanity checking code required) -- instead
  force drivers to pass the right variables to rfkill_alloc()

  * the documentation is hard to read because it always assumes the
  reader is completely clueless and contains way TOO MANY CAPS

  * the rfkill code needlessly uses a lot of locks and atomic
  operations in locked sections

  * fix LED trigger to actually change the LED when the radio state
  changes -- this wasn't done before

  Tested-by: Alan Jenkins
  Signed-off-by: Henrique de Moraes Holschuh [thinkpad]
  Signed-off-by: Johannes Berg
  Signed-off-by: John W. Linville

  Johannes Berg

  2009-06-04 02:06:13 +0800