Skip to content
Commits on Nov 8, 2013
  1. @vDorst
Commits on Aug 8, 2013
  1. Merge pull request #2 from warped-rudi/for-rabeeh

    Misc merges from Rudi.
    committed Aug 8, 2013
Commits on Aug 6, 2013
  1. @moinejf @warped-rudi

    stop permanent dovefb IRQs

    moinejf committed with warped-rudi Nov 18, 2012
  2. @warped-rudi
  3. @warped-rudi
  4. @warped-rudi
  5. @warped-rudi
  6. @warped-rudi
Commits on Jun 18, 2013
  1. Updated cubox_defconfig

    Added cgroups, kernel configu into /proc and a bunch of modules
    
    Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>
    committed Jun 18, 2013
Commits on Apr 16, 2013
  1. vmeta uio driver optimzation

    This is a fix imported from the Marvell original kernel (2.6.32.9).
    Using this patch while decoding using vmeta engine, CPU utilization dropped substiantially.
    
    Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>
    committed Apr 16, 2013
Commits on Mar 29, 2013
  1. Protect BMM_DUMP with the global mutex

    Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>
    committed Mar 29, 2013
Commits on Jan 29, 2013
  1. Wrong usage of BMM cache flushing

    Wrong usage of flushing API.
    Instead of using the dmac_map_area, dmac_flush_range must be used since the first is restricted to kernel space only and the latter can accept both kernel and user area.
    The reason is the BMM allocates and maps buffers into a user area where the addresses that can be used are not kernel.
    
    This fixes an issue that cache flushing BMM buffers allocated to vmeta makes a kernel panic
    
    Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>
    committed Jan 29, 2013
Commits on Dec 31, 2012
  1. @vDorst
  2. @vDorst
Commits on Dec 10, 2012
  1. @warped-rudi

    Blank screen on shutdown

    warped-rudi committed with Oct 23, 2012
  2. @warped-rudi

    Fixed audio stutter

    warped-rudi committed with Dec 9, 2012
  3. Prefer external clock on kirkwood-i2s

    When external clock is availbe, use it instead of the internal DCO.
    Also handle return values of unsupported rates
    
    Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>
    committed Dec 10, 2012
  4. @warped-rudi
  5. Changes Kirkwood SPDIF name

    change name of S/PDIF to SPDIF (to better suite alsa config files)
    
    Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>
    committed Dec 10, 2012
  6. Added combined access to i2c controller

    Adds combined access to i2C controller (i2c-mv64xxx.c).
    
    Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>
    committed Dec 10, 2012
  7. Merge branch 'master' of github.com:rabeeh/linux

    Conflicts:
    	arch/arm/mach-dove/common.c
    
    Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>
    committed Dec 10, 2012
  8. LK 3.6.8 doesn't like __udelay

    Instead use 10 times udelay(1000)
    
    Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>
    committed Dec 10, 2012
  9. Merge tag 'v3.6.9' into 3.6.9

    This is the 3.6.9 stable release
    
    Conflicts:
    	arch/arm/plat-orion/common.c
    	drivers/mmc/host/sdhci-dove.c
    committed Dec 10, 2012
Commits on Dec 3, 2012
  1. @gregkh

    Linux 3.6.9

    gregkh committed Dec 3, 2012
  2. @neilbrown @gregkh

    md/raid10: close race that lose writes lost when replacement completes.

    commit e7c0c3f upstream.
    
    When a replacement operation completes there is a small window
    when the original device is marked 'faulty' and the replacement
    still looks like a replacement.  The faulty should be removed and
    the replacement moved in place very quickly, bit it isn't instant.
    
    So the code write out to the array must handle the possibility that
    the only working device for some slot in the replacement - but it
    doesn't.  If the primary device is faulty it just gives up.  This
    can lead to corruption.
    
    So make the code more robust: if either  the primary or the
    replacement is present and working, write to them.  Only when
    neither are present do we give up.
    
    This bug has been present since replacement was introduced in
    3.3, so it is suitable for any -stable kernel since then.
    
    Reported-by: "George Spelvin" <linux@horizon.com>
    Cc: stable@vger.kernel.org
    Signed-off-by: NeilBrown <neilb@suse.de>
    Signed-off-by: George Spelvin <linux@horizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    neilbrown committed with gregkh Nov 22, 2012
  3. @gregkh

    mmc: sdhci-s3c: fix the wrong number of max bus clocks

    commit 5feb54a upstream.
    
    We can use up to four bus-clocks; but on module remove, we didn't
    disable the fourth bus clock.
    
    Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
    Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
    Signed-off-by: Chris Ball <cjb@laptop.org>
    Cc: Ben Hutchings <ben@decadent.org.uk>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Jaehoon Chung committed with gregkh Sep 19, 2012
  4. @shangw @gregkh

    powerpc/eeh: Lock module while handling EEH event

    commit feadf7c upstream.
    
    The EEH core is talking with the PCI device driver to determine the
    action (purely reset, or PCI device removal). During the period, the
    driver might be unloaded and in turn causes kernel crash as follows:
    
    EEH: Detected PCI bus error on PHB#4-PE#10000
    EEH: This PCI device has failed 3 times in the last hour
    lpfc 0004:01:00.0: 0:2710 PCI channel disable preparing for reset
    Unable to handle kernel paging request for data at address 0x00000490
    Faulting instruction address: 0xd00000000e682c90
    cpu 0x1: Vector: 300 (Data Access) at [c000000fc75ffa20]
        pc: d00000000e682c90: .lpfc_io_error_detected+0x30/0x240 [lpfc]
        lr: d00000000e682c8c: .lpfc_io_error_detected+0x2c/0x240 [lpfc]
        sp: c000000fc75ffca0
       msr: 8000000000009032
       dar: 490
     dsisr: 40000000
      current = 0xc000000fc79b88b0
      paca    = 0xc00000000edb0380	 softe: 0	 irq_happened: 0x00
        pid   = 3386, comm = eehd
    enter ? for help
    [c000000fc75ffca0] c000000fc75ffd30 (unreliable)
    [c000000fc75ffd30] c00000000004fd3c .eeh_report_error+0x7c/0xf0
    [c000000fc75ffdc0] c00000000004ee00 .eeh_pe_dev_traverse+0xa0/0x180
    [c000000fc75ffe70] c00000000004ffd8 .eeh_handle_event+0x68/0x300
    [c000000fc75fff00] c0000000000503a0 .eeh_event_handler+0x130/0x1a0
    [c000000fc75fff90] c000000000020138 .kernel_thread+0x54/0x70
    1:mon>
    
    The patch increases the reference of the corresponding driver modules
    while EEH core does the negotiation with PCI device driver so that the
    corresponding driver modules can't be unloaded during the period and
    we're safe to refer the callbacks.
    
    Reported-by: Alexey Kardashevskiy <aik@ozlabs.ru>
    Signed-off-by: Gavin Shan <shangw@linux.vnet.ibm.com>
    Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    [ herton: backported for 3.5, adjusted driver assignments, return 0
      instead of NULL, assume dev is not NULL ]
    Signed-off-by: Herton Ronaldo Krzesinski <herton.krzesinski@canonical.com>
    Cc: Ben Hutchings <ben@decadent.org.uk>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    shangw committed with gregkh Sep 17, 2012
  5. @taoma-tm @gregkh

    ext4: remove erroneous ext4_superblock_csum_set() in update_backups()

    commit bef53b0 upstream.
    
    The update_backups() function is used to backup all the metadata
    blocks, so we should not take it for granted that 'data' is pointed to
    a super block and use ext4_superblock_csum_set to calculate the
    checksum there.  In case where the data is a group descriptor block,
    it will corrupt the last group descriptor, and then e2fsck will
    complain about it it.
    
    As all the metadata checksums should already be OK when we do the
    backup, remove the wrong ext4_superblock_csum_set and it should be
    just fine.
    
    Reported-by: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Tao Ma <boyu.mt@taobao.com>
    Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
    Cc: Ben Hutchings <ben@decadent.org.uk>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    taoma-tm committed with gregkh Sep 20, 2012
  6. @mlauss @gregkh

    MPI: Fix compilation on MIPS with GCC 4.4 and newer

    commit a3cea98 upstream.
    
    Since 4.4 GCC on MIPS no longer recognizes the "h" constraint,
    leading to this build failure:
    
      CC      lib/mpi/generic_mpih-mul1.o
    lib/mpi/generic_mpih-mul1.c: In function 'mpihelp_mul_1':
    lib/mpi/generic_mpih-mul1.c:50:3: error: impossible constraint in 'asm'
    
    This patch updates MPI with the latest umul_ppm implementations for MIPS.
    
    Signed-off-by: Manuel Lauss <manuel.lauss@gmail.com>
    Cc: Linux-MIPS <linux-mips@linux-mips.org>
    Cc: Dmitry Kasatkin <dmitry.kasatkin@intel.com>
    Cc: James Morris <jmorris@namei.org>
    Patchwork: https://patchwork.linux-mips.org/patch/4612/
    Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
    Cc: Shuah Khan <shuah.khan@hp.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    mlauss committed with gregkh Nov 22, 2012
  7. @gregkh

    watchdog: using u64 in get_sample_period()

    commit 8ffeb9b upstream.
    
    In get_sample_period(), unsigned long is not enough:
    
      watchdog_thresh * 2 * (NSEC_PER_SEC / 5)
    
    case1:
      watchdog_thresh is 10 by default, the sample value will be: 0xEE6B2800
    
    case2:
     set watchdog_thresh is 20, the sample value will be: 0x1 DCD6 5000
    
    In case2, we need use u64 to express the sample period.  Otherwise,
    changing the threshold thru proc often can not be successful.
    
    Signed-off-by: liu chuansheng <chuansheng.liu@intel.com>
    Acked-by: Don Zickus <dzickus@redhat.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Shuah Khan <shuah.khan@hp.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Chuansheng Liu committed with gregkh Nov 26, 2012
  8. @gregkh

    mm: vmscan: check for fatal signals iff the process was throttled

    commit 50694c2 upstream.
    
    Commit 5515061 ("mm: throttle direct reclaimers if PF_MEMALLOC
    reserves are low and swap is backed by network storage") introduced a
    check for fatal signals after a process gets throttled for network
    storage.  The intention was that if a process was throttled and got
    killed that it should not trigger the OOM killer.  As pointed out by
    Minchan Kim and David Rientjes, this check is in the wrong place and too
    broad.  If a system is in am OOM situation and a process is exiting, it
    can loop in __alloc_pages_slowpath() and calling direct reclaim in a
    loop.  As the fatal signal is pending it returns 1 as if it is making
    forward progress and can effectively deadlock.
    
    This patch moves the fatal_signal_pending() check after throttling to
    throttle_direct_reclaim() where it belongs.  If the process is killed
    while throttled, it will return immediately without direct reclaim
    except now it will have TIF_MEMDIE set and will use the PFMEMALLOC
    reserves.
    
    Minchan pointed out that it may be better to direct reclaim before
    returning to avoid using the reserves because there may be pages that
    can easily reclaim that would avoid using the reserves.  However, we do
    no such targetted reclaim and there is no guarantee that suitable pages
    are available.  As it is expected that this throttling happens when
    swap-over-NFS is used there is a possibility that the process will
    instead swap which may allocate network buffers from the PFMEMALLOC
    reserves.  Hence, in the swap-over-nfs case where a process can be
    throtted and be killed it can use the reserves to exit or it can
    potentially use reserves to swap a few pages and then exit.  This patch
    takes the option of using the reserves if necessary to allow the process
    exit quickly.
    
    If this patch passes review it should be considered a -stable candidate
    for 3.6.
    
    Signed-off-by: Mel Gorman <mgorman@suse.de>
    Cc: David Rientjes <rientjes@google.com>
    Cc: Luigi Semenzato <semenzato@google.com>
    Cc: Dan Magenheimer <dan.magenheimer@oracle.com>
    Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
    Cc: Sonny Rao <sonnyrao@google.com>
    Cc: Minchan Kim <minchan@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: CAI Qian <caiqian@redhat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Mel Gorman committed with gregkh Nov 26, 2012
  9. @gregkh

    NFC: Fix nfc_llcp_local chained list insertion

    commit 16a78e9 upstream.
    
    list_add was called with swapped parameters
    
    Signed-off-by: Thierry Escande <thierry.escande@linux.intel.com>
    Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
    Signed-off-by: Peter Huewe <peterhuewe@gmx.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Thierry Escande committed with gregkh Oct 12, 2012
  10. @gregkh

    NFC: pn533: Fix mem leak in pn533_in_dep_link_up

    commit 70418e6 upstream.
    
    cmd is allocated in pn533_dep_link_up and passed as an arg to
    pn533_send_cmd_frame_async together with a complete cb.
    
    arg is passed to the cb and must be kfreed there.
    
    Signed-off-by: Waldemar Rymarkiewicz <waldemar.rymarkiewicz@tieto.com>
    Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
    Signed-off-by: Peter Huewe <peterhuewe@gmx.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Waldemar Rymarkiewicz committed with gregkh Oct 11, 2012
  11. @gregkh

    NFC: Fix pn533 target mode memory leak

    commit 5b412fd upstream.
    
    In target mode, sent sk_buff were not freed in pn533_tm_send_complete
    
    Signed-off-by: Thierry Escande <thierry.escande@linux.intel.com>
    Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
    Signed-off-by: Peter Huewe <peterhuewe@gmx.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Thierry Escande committed with gregkh Nov 15, 2012
  12. @gregkh

    NFC: pn533: Fix use after free

    commit 770f750 upstream.
    
    cmd was freed in pn533_dep_link_up regardless of
    pn533_send_cmd_frame_async return code. Cmd is passed as argument to
    pn533_in_dep_link_up_complete callback and should be freed there.
    
    Signed-off-by: Szymon Janc <szymon.janc@tieto.com>
    Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
    Signed-off-by: Peter Huewe <peterhuewe@gmx.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Szymon Janc committed with gregkh Oct 29, 2012
Something went wrong with that request. Please try again.