Doug / smarc-fsl-linux-kernel

31 Oct, 2013

5 commits

29 Oct, 2013

19 commits

20 Oct, 2013

4 commits

  • 207287595   staging: rtl8187se: checkpatch cleanups ... Browse Code »

    Fix the following checkpatch.pl errors:

    drivers/staging/rtl8187se/ieee80211/ieee80211_softmac.c:890: "foo* bar" should be "foo *bar"
    drivers/staging/rtl8187se/ieee80211/ieee80211_softmac.c:944: "foo* bar" should be "foo *bar"

    Signed-off-by: Teodora Baluta
    Signed-off-by: Greg Kroah-Hartman

    Teodora Baluta
     
  • 17ab33eed   staging: rtl8187se: fix static sparse warnings ... Browse Code »

    This patch fixes sparse warnings regarding functions that should be
    static in driver rtl8187se.

    Signed-off-by: Teodora Baluta
    Signed-off-by: Greg Kroah-Hartman

    Teodora Baluta
     
  • 8e87b1b3d   staging: rtl8187se: add missing __iomem annotation ... Browse Code »

    Fix the following type of sparse warnings:

    drivers/staging/rtl8187se/r8180_core.c:163:48: warning: incorrect type in argument 1 (different address spaces)
    drivers/staging/rtl8187se/r8180_core.c:163:48: expected void const volatile [noderef] *addr
    drivers/staging/rtl8187se/r8180_core.c:163:48: got unsigned char [usertype] *

    Signed-off-by: Teodora Baluta
    Signed-off-by: Greg Kroah-Hartman

    Teodora Baluta
     
  • 8b65c5bb0   staging: rtl8187se: use gfp_t instead of int ... Browse Code »

    Fix the following type of sparse warnings:

    drivers/staging/rtl8187se/ieee80211/ieee80211_tx.c:249:17: warning: incorrect type in argument 2 (different base types)
    drivers/staging/rtl8187se/ieee80211/ieee80211_tx.c:249:17: expected restricted gfp_t [usertype] flags
    drivers/staging/rtl8187se/ieee80211/ieee80211_tx.c:249:17: got int [signed] gfp_mask

    Signed-off-by: Teodora Baluta
    Signed-off-by: Greg Kroah-Hartman

    Teodora Baluta
     

12 Oct, 2013

2 commits

01 Oct, 2013

1 commit

26 Sep, 2013

2 commits

28 Aug, 2013

1 commit

24 Aug, 2013

1 commit

19 Jun, 2013

1 commit

05 May, 2013

1 commit

02 May, 2013

2 commits

  • 4a520d276   proc: Supply an accessor for getting the data from a PDE's parent ... Browse Code »

    Supply an accessor function for getting the private data from the parent
    proc_dir_entry struct of the proc_dir_entry struct associated with an inode.

    ReiserFS, for instance, stores the super_block pointer in the proc directory
    it makes for that super_block, and a pointer to the respective seq_file show
    function in each of the proc files in that directory.

    This allows a reduction in the number of file_operations structs, open
    functions and seq_operations structs required. The problem otherwise is that
    each show function requires two pieces of data but only has storage for one
    per PDE (and this has no release function).

    Signed-off-by: David Howells
    Acked-by: Mauro Carvalho Chehab
    Acked-by: Greg Kroah-Hartman
    cc: Jerry Chuang
    cc: Maxim Mikityanskiy
    cc: YAMANE Toshiaki
    cc: linux-wireless@vger.kernel.org
    cc: linux-scsi@vger.kernel.org
    cc: devel@driverdev.osuosl.org
    Signed-off-by: Al Viro

    David Howells
     
  • c4558a26f   rtl8187se: Use a dir under /proc/net/r8180/ ... Browse Code »

    Create a dir under /proc/net/r8180/ named for the device and create that
    device's files under there. This means that there won't be a problem for
    multiple devices in the system (if such is possible) and it means we don't
    need to save the 'device directory' PDE any more as we can just do a proc
    subtree removal.

    Signed-off-by: David Howells
    Acked-by: Greg Kroah-Hartman
    cc: Maxim Mikityanskiy
    cc: YAMANE Toshiaki
    cc: linux-wireless@vger.kernel.org
    cc: devel@driverdev.osuosl.org
    Signed-off-by: Al Viro

    David Howells
     

30 Apr, 2013

1 commit

  • 5ba02e355   rtl8187se: Don't use create_proc_read_entry() ... Browse Code »

    Don't use create_proc_read_entry() as that is deprecated, but rather use
    proc_create_data() and seq_file instead. Whilst we're at it, reduce the
    number of show functions where we can share them.

    Question: Do any of the registers read by proc_get_registers() have side
    effects upon reading? If so, locking will be required.

    Signed-off-by: David Howells
    cc: Greg Kroah-Hartman
    cc: Maxim Mikityanskiy
    cc: YAMANE Toshiaki
    cc: Bill Pemberton
    cc: Andrea Merello
    cc: linux-wireless@vger.kernel.org
    cc: devel@driverdev.osuosl.org
    Signed-off-by: Al Viro

    David Howells