Eric Lee / smarc-fsl-linux-kernel

07 Sep, 2011

1 commit

31 Mar, 2011

1 commit

22 Mar, 2011

1 commit

21 Oct, 2010

1 commit

30 Mar, 2010

1 commit

  • 5a0e3ad6a   include cleanup: Update gfp.h and slab.h includes to prepare for breaking implic… ... Browse Code »

    …it slab.h inclusion from percpu.h

    percpu.h is included by sched.h and module.h and thus ends up being
    included when building most .c files. percpu.h includes slab.h which
    in turn includes gfp.h making everything defined by the two files
    universally available and complicating inclusion dependencies.

    percpu.h -> slab.h dependency is about to be removed. Prepare for
    this change by updating users of gfp and slab facilities include those
    headers directly instead of assuming availability. As this conversion
    needs to touch large number of source files, the following script is
    used as the basis of conversion.

    http://userweb.kernel.org/~tj/misc/slabh-sweep.py

    The script does the followings.

    * Scan files for gfp and slab usages and update includes such that
    only the necessary includes are there. ie. if only gfp is used,
    gfp.h, if slab is used, slab.h.

    * When the script inserts a new include, it looks at the include
    blocks and try to put the new include such that its order conforms
    to its surrounding. It's put in the include block which contains
    core kernel includes, in the same order that the rest are ordered -
    alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
    doesn't seem to be any matching order.

    * If the script can't find a place to put a new include (mostly
    because the file doesn't have fitting include block), it prints out
    an error message indicating which .h file needs to be added to the
    file.

    The conversion was done in the following steps.

    1. The initial automatic conversion of all .c files updated slightly
    over 4000 files, deleting around 700 includes and adding ~480 gfp.h
    and ~3000 slab.h inclusions. The script emitted errors for ~400
    files.

    2. Each error was manually checked. Some didn't need the inclusion,
    some needed manual addition while adding it to implementation .h or
    embedding .c file was more appropriate for others. This step added
    inclusions to around 150 files.

    3. The script was run again and the output was compared to the edits
    from #2 to make sure no file was left behind.

    4. Several build tests were done and a couple of problems were fixed.
    e.g. lib/decompress_*.c used malloc/free() wrappers around slab
    APIs requiring slab.h to be added manually.

    5. The script was run on all .h files but without automatically
    editing them as sprinkling gfp.h and slab.h inclusions around .h
    files could easily lead to inclusion dependency hell. Most gfp.h
    inclusion directives were ignored as stuff from gfp.h was usually
    wildly available and often used in preprocessor macros. Each
    slab.h inclusion directive was examined and added manually as
    necessary.

    6. percpu.h was updated not to include slab.h.

    7. Build test were done on the following configurations and failures
    were fixed. CONFIG_GCOV_KERNEL was turned off for all tests (as my
    distributed build env didn't work with gcov compiles) and a few
    more options had to be turned off depending on archs to make things
    build (like ipr on powerpc/64 which failed due to missing writeq).

    * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
    * powerpc and powerpc64 SMP allmodconfig
    * sparc and sparc64 SMP allmodconfig
    * ia64 SMP allmodconfig
    * s390 SMP allmodconfig
    * alpha SMP allmodconfig
    * um on x86_64 SMP allmodconfig

    8. percpu.h modifications were reverted so that it could be applied as
    a separate patch and serve as bisection point.

    Given the fact that I had only a couple of failures from tests on step
    6, I'm fairly confident about the coverage of this conversion patch.
    If there is a breakage, it's likely to be something in one of the arch
    headers which should be easily discoverable easily on most builds of
    the specific arch.

    Signed-off-by: Tejun Heo <tj@kernel.org>
    Guess-its-ok-by: Christoph Lameter <cl@linux-foundation.org>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>

    Tejun Heo
     

06 Dec, 2009

1 commit

07 Apr, 2009

2 commits

30 Mar, 2009

5 commits

18 Oct, 2008

1 commit

12 Oct, 2008

1 commit

25 Apr, 2008

1 commit

03 Feb, 2008

1 commit

26 Sep, 2006

1 commit

25 Jun, 2006

1 commit

25 Mar, 2006

1 commit

24 Mar, 2006

1 commit

  • 279a022d4   [PATCH] I2C: Drop unneeded i2c-dev.h includes ... Browse Code »

    Several media/video and sound drivers include i2c-dev.h while they
    don't need it at all. Clean it up.

    This header file is really only needed by i2c-dev.c and
    compat_ioctl.c, other drivers should never need it.

    Signed-off-by: Jean Delvare
    Signed-off-by: Greg Kroah-Hartman

    Jean Delvare
     

12 Jan, 2006

1 commit

06 Jan, 2006

4 commits

17 Oct, 2005

2 commits

  • de21eb63a   [PATCH] fix black/white-only svideo input in vpx3220 decoder ... Browse Code »

    Fix the fact that the svideo input will only give input in black/white in
    some circumstances. Reason is that in the PCI controller driver (zr36067),
    after setting input, we reset norm, which overwrites the input register
    with the default. This patch makes it always set the correct value for the
    input when changing norm.

    Signed-off-by: Ronald S. Bultje
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Ronald S. Bultje
     
  • 9b3acc21d   [PATCH] fix vpx3220 offset issue in SECAM ... Browse Code »

    Fix bug #5404 in kernel bugzilla.

    It basically updates the vpx3220 initialization tables with some newer
    values that we've had in CVS for a while (and that, for some reason, never
    ended up in the kernel... must've gotten lost). Those fix a ~16 pixels
    noise at the top of the picture in at least SECAM, although (now that I
    think about it) PAL was probably affected, also.

    Signed-off-by: Ronald S. Bultje
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Ronald S. Bultje
     

06 Sep, 2005

1 commit

  • 9fc6adfa9   [PATCH] hwmon: hwmon vs i2c, second round (01/11) ... Browse Code »

    Add support for kind-forced addresses to i2c_probe, like i2c_detect
    has for (essentially) hardware monitoring drivers.

    Note that this change will slightly increase the size of the drivers
    using I2C_CLIENT_INSMOD, with no immediate benefit. This is a
    requirement if we want to merge i2c_probe and i2c_detect though, and
    seems a reasonable price to pay in comparison with the previous
    cleanups which saved much more than that (such as the i2c-isa cleanup
    or the i2c address ranges removal.)

    Signed-off-by: Jean Delvare
    Signed-off-by: Greg Kroah-Hartman

    Jean Delvare
     

22 Jun, 2005

2 commits

  • 68cc9d0b7   [PATCH] I2C: Merge unused address lists in some video drivers ... Browse Code »

    On top of my previous patch which removes the use of address ranges in
    video i2c drivers, this one can save an additional few bytes of memory.
    Most of these drivers which do not use I2C_CLIENT_INSMOD initialize the
    unused address lists in a less than optimal way. This patch simply
    optimizes this, by using a single one-element list instead of 3
    different lists with two elements each.

    This saves an average 63 bytes on these drivers.

    Signed-off-by: Jean Delvare
    Signed-off-by: Greg Kroah-Hartman

    diff -ruN linux-2.6.12-rc1-bk5.orig/drivers/media/video/adv7170.c linux-2.6.12-rc1-bk5/drivers/media/video/adv7170.c

    Jean Delvare
     
  • b3d5496ea   [PATCH] I2C: Kill address ranges in non-sensors i2c chip drivers ... Browse Code »

    Some months ago, you killed the address ranges mechanism from all
    sensors i2c chip drivers (both the module parameters and the in-code
    address lists). I think it was a very good move, as the ranges can
    easily be replaced by individual addresses, and this allowed for
    significant cleanups in the i2c core (let alone the impressive size
    shrink for all these drivers).

    Unfortunately you did not do the same for non-sensors i2c chip drivers.
    These need the address ranges even less, so we could get rid of the
    ranges here as well for another significant i2c core cleanup. Here comes
    a patch which does just that. Since the process is exactly the same as
    what you did for the other drivers set already, I did not split this one
    in parts.

    A documentation update is included.

    The change saves 308 bytes in the i2c core, and an average 1382 bytes
    for chip drivers which use I2C_CLIENT_INSMOD, 126 bytes for those which
    do not.

    This change is required if we want to merge the sensors and non-sensors
    i2c code (and we want to do this).

    Signed-off-by: Jean Delvare
    Signed-off-by: Greg Kroah-Hartman

    Index: gregkh-2.6/Documentation/i2c/writing-clients
    ===================================================================

    Jean Delvare
     

17 Apr, 2005

1 commit

  • 1da177e4c   Linux-2.6.12-rc2 ... Browse Code »

    Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds