01 Oct, 2009

1 commit


29 Sep, 2009

2 commits

  • Since 2.6.29 the PCI PM core have been restoring the standard
    configuration registers of PCI devices in the early phase of
    resume. In particular, PCI devices without drivers have been handled
    this way since commit 355a72d75b3b4f4877db4c9070c798238028ecb5
    (PCI: Rework default handling of suspend and resume). Unfortunately,
    this leads to post-resume problems with CardBus devices which cannot
    be accessed in the early phase of resume, because the sockets they
    are on have not been woken up yet at that point.

    To solve this problem, move the yenta socket resume to the early
    phase of resume and, analogously, move the suspend of it to the late
    phase of suspend. Additionally, remove some unnecessary PCI code
    from the yenta socket's resume routine.

    Fixes http://bugzilla.kernel.org/show_bug.cgi?id=13092, which is a
    post-2.6.28 regression.

    Signed-off-by: Rafael J. Wysocki
    Reported-by: Florian
    Cc: stable@kernel.org

    Rafael J. Wysocki
     
  • pcmcia_socket_dev_suspend() doesn't use its second argument, so it
    may be dropped safely.

    This change is necessary for the subsequent yenta suspend/resume fix.

    Signed-off-by: Rafael J. Wysocki
    Cc: stable@kernel.org

    Rafael J. Wysocki
     

25 Sep, 2009

1 commit


23 Sep, 2009

1 commit


22 Sep, 2009

3 commits


16 Sep, 2009

7 commits


10 Sep, 2009

4 commits


09 Jul, 2009

1 commit

  • Commit 5fd29d6ccbc98884569d6f3105aeca70858b3e0f ("printk: clean up
    handling of log-levels and newlines") changed printk semantics. printk
    lines with multiple KERN_ prefixes are no longer emitted as
    before the patch.

    is now included in the output on each additional use.

    Remove all uses of multiple KERN_s in formats.

    Signed-off-by: Joe Perches
    Signed-off-by: Linus Torvalds

    Joe Perches
     

03 Jul, 2009

1 commit


17 Jun, 2009

2 commits

  • * akpm: (182 commits)
    fbdev: bf54x-lq043fb: use kzalloc over kmalloc/memset
    fbdev: *bfin*: fix __dev{init,exit} markings
    fbdev: *bfin*: drop unnecessary calls to memset
    fbdev: bfin-t350mcqb-fb: drop unused local variables
    fbdev: blackfin has __raw I/O accessors, so use them in fb.h
    fbdev: s1d13xxxfb: add accelerated bitblt functions
    tcx: use standard fields for framebuffer physical address and length
    fbdev: add support for handoff from firmware to hw framebuffers
    intelfb: fix a bug when changing video timing
    fbdev: use framebuffer_release() for freeing fb_info structures
    radeon: P2G2CLK_ALWAYS_ONb tested twice, should 2nd be P2G2CLK_DAC_ALWAYS_ONb?
    s3c-fb: CPUFREQ frequency scaling support
    s3c-fb: fix resource releasing on error during probing
    carminefb: fix possible access beyond end of carmine_modedb[]
    acornfb: remove fb_mmap function
    mb862xxfb: use CONFIG_OF instead of CONFIG_PPC_OF
    mb862xxfb: restrict compliation of platform driver to PPC
    Samsung SoC Framebuffer driver: add Alpha Channel support
    atmel-lcdc: fix pixclock upper bound detection
    offb: use framebuffer_alloc() to allocate fb_info struct
    ...

    Manually fix up conflicts due to kmemcheck in mm/slab.c

    Linus Torvalds
     
  • There are some places to be able to use printk_once instead of hard coding.

    Signed-off-by: Minchan Kim
    Cc: Dominik Brodowski
    Cc: David S. Miller
    Cc: Ingo Molnar
    Cc: KOSAKI Motohiro
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Minchan Kim
     

16 Jun, 2009

2 commits

  • In the near future, the driver core is going to not allow direct access
    to the driver_data pointer in struct device. Instead, the functions
    dev_get_drvdata() and dev_set_drvdata() should be used. These functions
    have been around since the beginning, so are backwards compatible with
    all older kernel versions.

    Cc: linux-pcmcia@lists.infradead.org
    Cc: Dominik Brodowski
    Signed-off-by: Greg Kroah-Hartman

    Greg Kroah-Hartman
     
  • We're going to remove the FIRMWARE_NAME_MAX definition in order to avoid any
    firmware name length restriction.
    With the FIRMWARE_NAME_MAX removal, the ds.c reference becomes useless as we
    dont need to check for the firmware name length anymore.

    Signed-off-by: Samuel Ortiz
    Cc: Dominik Brodowski
    Signed-off-by: Greg Kroah-Hartman

    Samuel Ortiz
     

05 Jun, 2009

1 commit


24 Apr, 2009

1 commit


02 Apr, 2009

1 commit


29 Mar, 2009

1 commit


28 Mar, 2009

2 commits


25 Mar, 2009

3 commits


16 Mar, 2009

1 commit


09 Mar, 2009

3 commits


13 Jan, 2009

1 commit

  • Convert arch/powerpc/ over to long long based u64:

    -#ifdef __powerpc64__
    -# include
    -#else
    -# include
    -#endif
    +#include

    This will avoid reoccuring spurious warnings in core kernel code that
    comes when people test on their own hardware. (i.e. x86 in ~98% of the
    cases) This is what x86 uses and it generally helps keep 64-bit code
    32-bit clean too.

    [Adjusted to not impact user mode (from paulus) - sfr]

    Signed-off-by: Ingo Molnar
    Signed-off-by: Stephen Rothwell
    Signed-off-by: Benjamin Herrenschmidt

    Ingo Molnar
     

18 Dec, 2008

1 commit