Skip to content
Commits on Jun 17, 2012
Commits on Jun 16, 2012
  1. v1.1 config

  2. cpufreq_pegasusq: remove averaging of the average rq

    the reason of the additional averaging was to evaluate the runqueue for the total sampling interval instead of single sampling window. However, some peole reported lagginess and I suspect it may be related with this one. so, let's try to disable it and see if it helps.
    + some additional changes to make the governor more responsive.
  3. mach-exynod: stand-hotplug: fix max and min frequency levels which pr…

    …events other cores kicking in because of the modified freq table
Commits on Jun 15, 2012
  1. mmc: disable MMC_CAP_ERASE for MACH_U1 in case I try to build this re…

    …po for s2
    and build script + tiny fix in tmu for s2
  2. input: gpio_keys: make homekey press count and max delay between pres…

    …ses (to toggle mdnie negative effect) static variables to be able to configure them with kmemhelper
  3. Revert "testing compiler optimizations"

    This reverts commit 8abf890.
  4. Revert "introduce .arch_extension sec directive and some other "exter…

    …n inline" fixes for linaro toolchain compatibility"
    This reverts commit 8ffe1d0.
Commits on Jun 14, 2012
  1. introduce .arch_extension sec directive and some other "extern inline…

    …" fixes for linaro toolchain compatibility
  2. v1.0 config

  3. @avagin

    sched: Don't call task_group() too many times in set_task_rq()

    avagin committed with
    It improves perfomance, especially if autogroup is enabled.
    The size of set_task_rq() was 0x180 and now it is 0xa0.
    Signed-off-by: Andrew Vagin <>
    Acked-by: Paul Turner <>
    Signed-off-by: Peter Zijlstra <>
    Signed-off-by: Ingo Molnar <>
  4. kernel: make an exception in module loading to load proprietary modules

    This is the easiest way to bypass module_layout check to be able to load proprietery exfat modules without making any change on them.
Commits on Jun 13, 2012
  1. @JeffMoyer

    iosched: prevent aliased requests from starving other I/O

    JeffMoyer committed with
    Hi, Jens,
    If you recall, I posted an RFC patch for this back in July of last year:
    The basic problem is that a process can issue a never-ending stream of
    async direct I/Os to the same sector on a device, thus starving out
    other I/O in the system (due to the way the alias handling works in both
    cfq and deadline).  The solution I proposed back then was to start
    dispatching from the fifo after a certain number of aliases had been
    dispatched.  Vivek asked why we had to treat aliases differently at all,
    and I never had a good answer.  So, I put together a simple patch which
    allows aliases to be added to the rb tree (it adds them to the right,
    though that doesn't matter as the order isn't guaranteed anyway).  I
    think this is the preferred solution, as it doesn't break up time slices
    in CFQ or batches in deadline.  I've tested it, and it does solve the
    starvation issue.  Let me know what you think.
    Signed-off-by: Jeff Moyer <>
    Signed-off-by: Jens Axboe <>
  2. RWSEM_XCHGADD_ALGORITHM for ARM (R/W semaphores implemented using ARM…

    … atomic functions) by CodeAurora
  3. lib/sha1.c: quiet sparse noise about symbol not declared

    H Hartley Sweeten committed with
    Include <linux/cryptohash.h> to pickup the declarations for sha_transform
    and sha_init to quite the sparse noise:
      warning: symbol 'sha_transform' was not declared. Should it be static?
      warning: symbol 'sha_init' was not declared. Should it be static?
    Signed-off-by: H Hartley Sweeten <>
    Acked-by: Mandeep Singh Baines <>
    Signed-off-by: Linus Torvalds <>
  4. @torvalds

    arm: remove stale export of 'sha_transform'

    torvalds committed with
    The generic library code already exports the generic function, this was
    left-over from the ARM-specific version that just got removed.
    Signed-off-by: Linus Torvalds <>
Commits on Jun 12, 2012
  1. @torvalds

    arm: remove "optimized" SHA1 routines

    torvalds committed with
    Since commit 1eb19a12bd22 ("lib/sha1: use the git implementation of
    SHA-1"), the ARM SHA1 routines no longer work.  The reason? They
    depended on the larger 320-byte workspace, and now the sha1 workspace is
    just 16 words (64 bytes).  So the assembly version would overwrite the
    stack randomly.
    The optimized asm version is also probably slower than the new improved
    C version, so there's no reason to keep it around.  At least that was
    the case in git, where what appears to be the same assembly language
    version was removed two years ago because the optimized C BLK_SHA1 code
    was faster.
    Reported-and-tested-by: Joachim Eastwood <>
    Cc: Andreas Schwab <>
    Cc: Nicolas Pitre <>
    Signed-off-by: Linus Torvalds <>
  2. lib/sha1: use the git implementation of SHA-1

    Mandeep Singh Baines committed with
    For ChromiumOS, we use SHA-1 to verify the integrity of the root
    filesystem.  The speed of the kernel sha-1 implementation has a major
    impact on our boot performance.
    To improve boot performance, we investigated using the heavily optimized
    sha-1 implementation used in git.  With the git sha-1 implementation, we
    see a 11.7% improvement in boot time.
    10 reboots, remove slowest/fastest.
      Mean: 6.58 seconds Stdev: 0.14
    After (with git sha-1, this patch):
      Mean: 5.89 seconds Stdev: 0.07
    The other cool thing about the git SHA-1 implementation is that it only
    needs 64 bytes of stack for the workspace while the original kernel
    implementation needed 320 bytes.
    Signed-off-by: Mandeep Singh Baines <>
    Cc: Ramsay Jones <>
    Cc: Nicolas Pitre <>
    Cc: Herbert Xu <>
    Cc: David S. Miller <>
    Signed-off-by: Linus Torvalds <>
Commits on Jun 11, 2012
  1. regulator: max77686: make max77686 less chatty. we can use dynamic_de…

    …bug later if we need these debug messages
Something went wrong with that request. Please try again.