Permalink
Commits on Aug 10, 2010
  1. @gregkh

    Linux 2.6.35.1

    gregkh committed Aug 10, 2010
  2. @ickle @gregkh

    drm/i915: Check overlay stride errata for i830 and i845

    commit a1efd14 upstream.
    
    Apparently i830 and i845 cannot handle any stride that is not a multiple
    of 256, unlike their brethren which do support 64 byte aligned strides.
    
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    Signed-off-by: Eric Anholt <eric@anholt.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    ickle committed with gregkh Jul 12, 2010
  3. @ickle @gregkh

    drm/i915: Unset cursor if out-of-bounds upon mode change (v4)

    commit cda4b7d upstream.
    
    The docs warn that to position the cursor such that no part of it is
    visible on the pipe is an undefined operation. Avoid such circumstances
    upon changing the mode, or at any other time, by unsetting the cursor if
    it moves out of bounds.
    
    "For normal high resolution display modes, the cursor must have at least a
    single pixel positioned over the active screen.” (p143, p148 of the hardware
    registers docs).
    
    Fixes:
    
      Bug 24748 - [965G] Graphics crashes when resolution is changed with KMS
                  enabled
      https://bugs.freedesktop.org/show_bug.cgi?id=24748
    
    v2: Only update the cursor registers if they change.
    v3: Fix the unsigned comparision of x,y against width,height.
    v4: Always set CUR.BASE or else the cursor may become corrupt.
    
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    Reported-by: Christian Eggers <ceggers@gmx.de>
    Cc: Christopher James Halse Rogers  <chalserogers@gmail.com>
    Signed-off-by: Eric Anholt <eric@anholt.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    ickle committed with gregkh Jul 9, 2010
  4. @gregkh

    drm/radeon/kms: handle the case of no active displays properly in the…

    … bandwidth code
    
    commit e06b14e upstream.
    
    Logic was:
    if (mode0 && mode1)
    else if (mode0)
    else
    
    Should be:
    if (mode0 && mode1)
    else if (mode0)
    else if (mode1)
    
    Otherwise we may end up calculating the priority regs with
    unitialized values.
    
    Fixes:
    https://bugzilla.kernel.org/show_bug.cgi?id=16492
    
    Signed-off-by: Alex Deucher <alexdeucher@gmail.com>
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Alex Deucher committed with gregkh Aug 2, 2010
  5. @gregkh

    drm/radeon/kms/r7xx: add workaround for hw issue with HDP flush

    commit 812d046 upstream.
    
    Use of HDP_*_COHERENCY_FLUSH_CNTL can cause a hang in certain
    situations.  Add workaround.
    
    Signed-off-by: Alex Deucher <alexdeucher@gmail.com>
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Alex Deucher committed with gregkh Jul 26, 2010
  6. @gregkh

    drm/radeon: fall back to GTT if bo creation/validation in VRAM fails.

    commit e376573 upstream.
    
    This fixes a problem where on low VRAM cards we'd run out of space for validation.
    
    [airlied: Tested on my M7, Thinkpad T42, compiz works with no problems.]
    
    Signed-off-by: Michel Dänzer <daenzer@vmware.com>
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Michel Dänzer committed with gregkh Jul 8, 2010
  7. @gregkh

    drm/radeon: add new pci ids

    commit 1297c05 upstream.
    
    New evergreen and r7xx ids.
    
    Signed-off-by: Alex Deucher <alexdeucher@gmail.com>
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Alex Deucher committed with gregkh Aug 4, 2010
  8. @gregkh

    xen: drop xen_sched_clock in favour of using plain wallclock time

    commit 8a22b99 upstream.
    
    xen_sched_clock only counts unstolen time.  In principle this should
    be useful to the Linux scheduler so that it knows how much time a process
    actually consumed.  But in practice this doesn't work very well as the
    scheduler expects the sched_clock time to be synchronized between
    cpus.  It also uses sched_clock to measure the time a task spends
    sleeping, in which case "unstolen time" isn't meaningful.
    
    So just use plain xen_clocksource_read to return wallclock nanoseconds
    for sched_clock.
    
    Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Jeremy Fitzhardinge committed with gregkh Jul 12, 2010
  9. @gregkh

    SCSI: enclosure: fix error path - actually return ERR_PTR() on error

    commit a91c1be upstream.
    
    we also need to clean up and free the cdev.
    
    Reported-by: Jani Nikula <ext-jani.1.nikula@nokia.com>
    Signed-off-by: James Bottomley <James.Bottomley@suse.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    James Bottomley committed with gregkh Mar 12, 2010
  10. @gregkh

    CRED: Fix RCU warning due to previous patch fixing __task_cred()'s ch…

    …ecks
    
    commit 694f690 upstream.
    
    Commit 8f92054 ("CRED: Fix __task_cred()'s lockdep check and banner
    comment") fixed the lockdep checks on __task_cred().  This has shown up
    a place in the signalling code where a lock should be held - namely that
    check_kill_permission() requires its callers to hold the RCU lock.
    
    Fix group_send_sig_info() to get the RCU read lock around its call to
    check_kill_permission().
    
    Without this patch, the following warning can occur:
    
      ===================================================
      [ INFO: suspicious rcu_dereference_check() usage. ]
      ---------------------------------------------------
      kernel/signal.c:660 invoked rcu_dereference_check() without protection!
      ...
    
    Reported-by: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
    Signed-off-by: David Howells <dhowells@redhat.com>
    Acked-by: Oleg Nesterov <oleg@redhat.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    David Howells committed with gregkh Aug 4, 2010
  11. @linvjw @gregkh

    mac80211: avoid scheduling while atomic in mesh_rx_plink_frame

    commit c937019 upstream.
    
    While mesh_rx_plink_frame holds sta->lock...
    
    mesh_rx_plink_frame ->
    	mesh_plink_inc_estab_count ->
    		ieee80211_bss_info_change_notify
    
    ...but ieee80211_bss_info_change_notify is allowed to sleep.  A driver
    taking advantage of that allowance can cause a scheduling while
    atomic bug.  Similar paths exist for mesh_plink_dec_estab_count,
    so work around those as well.
    
    http://bugzilla.kernel.org/show_bug.cgi?id=16099
    
    Also, correct a minor kerneldoc comment error (mismatched function names).
    
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    linvjw committed with gregkh Jun 21, 2010
  12. @jmberg @gregkh

    cfg80211: don't get expired BSSes

    commit ccb6c13 upstream.
    
    When kernel-internal users use cfg80211_get_bss()
    to get a reference to a BSS struct, they may end
    up getting one that would have been removed from
    the list if there had been any userspace access
    to the list. This leads to inconsistencies and
    problems.
    
    Fix it by making cfg80211_get_bss() ignore BSSes
    that cfg80211_bss_expire() would remove.
    
    Fixes http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2180
    
    Reported-by: Jiajia Zheng <jiajia.zheng@intel.com>
    Tested-by: Jiajia Zheng <jiajia.zheng@intel.com>
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    jmberg committed with gregkh Jul 13, 2010
  13. @jmberg @gregkh

    cfg80211: ignore spurious deauth

    commit 643f82e upstream.
    
    Ever since mac80211/drivers are no longer
    fully in charge of keeping track of the
    auth status, trying to make them do so will
    fail. Instead of warning and reporting the
    deauthentication to userspace, cfg80211 must
    simply ignore it so that spurious
    deauthentications, e.g. before starting
    authentication, aren't seen by userspace as
    actual deauthentications.
    
    Reported-by: Paul Stewart <pstew@google.com>
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    jmberg committed with gregkh Jul 12, 2010
  14. @lwfinger @gregkh

    ssb: Handle alternate SSPROM location

    commit 9d1ac34 upstream.
    
    In kernel Bugzilla #15825 (2 users), in a wireless mailing list thread
    (http://lists.infradead.org/pipermail/b43-dev/2010-May/000124.html), and on a
    netbook owned by John Linville
    (http://marc.info/?l=linux-wireless&m=127230751408818&w=4), there are reports
    of ssb failing to detect an SPROM at the normal location. After studying the
    MMIO trace dump for the Broadcom wl driver, it was determined that the affected
    boxes had a relocated SPROM.
    
    This patch fixes all systems that have reported this problem.
    
    Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    lwfinger committed with gregkh May 15, 2010
  15. @sgruszka @gregkh

    iwlwifi: fix scan abort

    commit d28232b upstream.
    
    Fix possible double priv->mutex lock introduced by commit
    a69b03e
    "iwlwifi: cancel scan watchdog in iwl_bg_abort_scan" .
    We can not call cancel_delayed_work_sync(&priv->scan_check) with
    priv->mutex locked because workqueue function iwl_bg_scan_check()
    take that lock internally.
    
    We do not need to synchronize when canceling priv->scan_check work.
    We can avoid races (sending double abort command or send no
    command at all) using STATUS_SCAN_ABORT bit. Moreover
    current iwl_bg_scan_check() code seems to be broken, as
    we should not send abort commands when currently aborting.
    
    Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    sgruszka committed with gregkh Jul 29, 2010
  16. @gregkh

    ath9k_hw: fix antenna diversity on AR9285

    commit 601e0cb upstream.
    
    On AR9285, the antenna switch configuration register uses more than just
    16 bits. Because of an arbitrary mask applied to the EEPROM value that
    stores this configuration, diversity was broken in some cases, leading
    to a significant degradation in signal strength.
    Fix this by changing the callback to return a 32 bit value and remove
    the arbitrary mask.
    
    Signed-off-by: Felix Fietkau <nbd@openwrt.org>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Felix Fietkau committed with gregkh Jul 11, 2010
  17. @gregkh

    ath9k: fix yet another buffer leak in the tx aggregation code

    commit 4cee786 upstream.
    
    When an aggregation session is being cleaned up, while the tx status
    for some frames is being processed, the TID is flushed and its buffers
    are sent out.
    
    Unfortunately that left the pending un-acked frames unprocessed, thus
    leaking buffers. Fix this by reordering the code so that those frames
    are processed first, before the TID is flushed.
    
    Signed-off-by: Felix Fietkau <nbd@openwrt.org>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Felix Fietkau committed with gregkh Jul 23, 2010
  18. @gregkh

    ath9k: fix TSF after reset on AR913x

    commit f860d52 upstream.
    
    When issuing a reset, the TSF value is lost in the hardware because of
    the 913x specific cold reset. As with some AR9280 cards, the TSF needs
    to be preserved in software here.
    
    Additionally, there's an issue that frequently prevents a successful
    TSF write directly after the chip reset. In this case, repeating the
    TSF write after the initval-writes usually works.
    
    This patch detects failed TSF writes and recovers from them, taking
    into account the delay caused by the initval writes.
    
    Signed-off-by: Felix Fietkau <nbd@openwrt.org>
    Reported-by: Björn Smedman <bjorn.smedman@venatech.se>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Felix Fietkau committed with gregkh Jun 30, 2010
  19. @gregkh

    ath9k: another fix for the A-MPDU buffer leak

    commit 31e79a5 upstream.
    
    The patch 'ath9k: fix a buffer leak in A-MPDU completion' addressed the
    issue of running out of buffers/descriptors in the tx path if a STA is
    deleted while tx status feedback is still pending.
    The remaining issue is that the skbs of the buffers are not reclaimed,
    leaving a memory leak.
    This patch fixes this issue by running the buffers through
    ath_tx_complete_buf(), ensuring that the pending frames counter is also
    updated.
    
    Signed-off-by: Felix Fietkau <nbd@openwrt.org>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Felix Fietkau committed with gregkh Jul 12, 2010
  20. @gregkh

    ath9k: fix a buffer leak in A-MPDU completion

    commit 73e1946 upstream.
    
    When ath_tx_complete_aggr() is called, it's responsible for returning
    all buffers in the linked list. This was not done when the STA lookup
    failed, leading to a race condition that could leak a few buffers when
    a STA just disconnected.
    Fix this by immediately returning all buffers to the free list in this case.
    
    Signed-off-by: Felix Fietkau <nbd@openwrt.org>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Felix Fietkau committed with gregkh Jul 7, 2010
  21. @gregkh

    ath9k: fix retry count for A-MPDU rate control status reports

    commit 78c4653 upstream.
    
    The 'bf_retries' field of the ath_buf structure was used for both
    software retries (AMPDU subframes) and hardware retries (legacy
    frames). This led to a wrong retry count being reported for the A-MPDU
    rate control stats.
    This patch changes the code to no longer use bf_retries for reporting
    retry counts, but instead always using the real on-chip retry count
    from the ath_tx_status.
    Additionally, if the first subframe of an A-MPDU was not acked, the tx
    status report is submitted along with the first acked subframe, which
    may not contain the correct rates in the tx info.
    This is easily corrected by saving the tx rate info before looping over
    subframes, and then copying it back once the A-MPDU status report is
    submitted.
    In my tests this change improves throughput visibly.
    
    Signed-off-by: Felix Fietkau <nbd@openwrt.org>
    Reported-by: Björn Smedman <bjorn.smedman@venatech.se>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Felix Fietkau committed with gregkh Jun 24, 2010
  22. @gregkh

    ath9k_hw: fix an off-by-one error in the PDADC boundaries calculation

    commit 03b4776 upstream.
    
    PDADC values were only generated for values surrounding the target
    index, however not for the target index itself, leading to a minor
    error in the generated curve.
    
    Signed-off-by: Felix Fietkau <nbd@openwrt.org>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Felix Fietkau committed with gregkh Jul 11, 2010
  23. @gregkh

    ath9k_hw: fix a sign error in the IQ calibration code

    commit 2339901 upstream.
    
    Signed-off-by: Felix Fietkau <nbd@openwrt.org>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Felix Fietkau committed with gregkh Jul 11, 2010
  24. @gregkh

    ath9k_hw: prevent a fast channel change after a rx DMA stuck issue

    commit 9cc2f3e upstream.
    
    If the receive path gets stuck, a full hardware reset is necessary to
    recover from it. If this happens during a scan, the whole scan might fail,
    as each channel change bypasses the full reset sequence.
    Fix this by resetting the fast channel change flag if stopping the
    receive path fails.
    
    This will reduce the number of error messages that look like this:
    ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
    
    Signed-off-by: Felix Fietkau <nbd@openwrt.org>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Felix Fietkau committed with gregkh Jul 11, 2010
  25. @gregkh

    ath9k: fix a potential buffer leak in the STA teardown path

    commit 2b40994 upstream.
    
    It looks like it might be possible for a TID to be paused, while still
    holding some queued buffers, however ath_tx_node_cleanup currently only
    iterates over active TIDs.
    Fix this by always checking every allocated TID for the STA that is being
    cleaned up.
    
    Signed-off-by: Felix Fietkau <nbd@openwrt.org>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Felix Fietkau committed with gregkh Jul 7, 2010
  26. @linvjw @gregkh

    ath9k: enable serialize_regmode for non-PCIE AR9160

    commit 4c85ab1 upstream.
    
    https://bugzilla.kernel.org/show_bug.cgi?id=16476
    
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Acked-by: Luis R. Rodriguez <lrodriguez@atheros.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    linvjw committed with gregkh Jul 28, 2010
  27. @gregkh

    igb: Use only a single Tx queue in SR-IOV mode

    commit 5fa8517 upstream.
    
    The 82576 expects the second rx queue in any pool to receive L2 switch
    loop back packets sent from the second tx queue in another pool.  The
    82576 VF driver does not enable the second rx queue so if the PF driver
    sends packets destined to a VF from its second tx queue then the VF
    driver will never see them.  In SR-IOV mode limit the number of tx queues
    used by the PF driver to one. This patch fixes a bug reported in which
    the PF cannot communciate with the VF and should be considered for 2.6.34
    stable.
    
    Signed-off-by: Greg Rose <gregory.v.rose@intel.com>
    Tested-by: Jeff Pieper <jeffrey.e.pieper@intel.com>
    Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Greg Rose committed with gregkh Jul 1, 2010
  28. @error27 @gregkh

    9p: strlen() doesn't count the terminator

    commit 5c4bfa1 upstream.
    
    This is an off by one bug because strlen() doesn't count the NULL
    terminator.  We strcpy() addr into a fixed length array of size
    UNIX_PATH_MAX later on.
    
    The addr variable is the name of the device being mounted.
    
    Signed-off-by: Dan Carpenter <error27@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    error27 committed with gregkh Jul 9, 2010
  29. @bwallan @gregkh

    e1000e: 82577/82578 PHY register access issues

    commit ff847ac upstream.
    
    The MAC-PHY interconnect on 82577/82578 uses a power management feature
    (called K1) which must be disabled when in 1Gbps due to a hardware issue on
    these parts.  The #define bit setting used to enable/disable K1 is
    incorrect and can cause PHY register accesses to stop working altogether
    until the next device reset.  This patch sets the register correctly.
    
    This issue is present in kernels since 2.6.32.
    
    Signed-off-by: Bruce Allan <bruce.w.allan@intel.com>
    Tested-by: Jeff Pieper <jeffrey.e.pieper@intel.com>
    Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    bwallan committed with gregkh Jul 27, 2010
  30. @gregkh

    e1000e: don't inadvertently re-set INTX_DISABLE

    commit 36f2407 upstream.
    
    Should e1000_test_msi() fail to see an msi interrupt, it attempts to
    fallback to legacy INTx interrupts. But an error in the code may prevent
    this from happening correctly.
    
    Before calling e1000_test_msi_interrupt(), e1000_test_msi() disables SERR
    by clearing the SERR bit from the just read PCI_COMMAND bits as it writes
    them back out.
    
    Upon return from calling e1000_test_msi_interrupt(), it re-enables SERR
    by writing out the version of PCI_COMMAND it had previously read.
    
    The problem with this is that e1000_test_msi_interrupt() calls
    pci_disable_msi(), which eventually ends up in pci_intx(). And because
    pci_intx() was called with enable set to 1, the INTX_DISABLE bit gets
    cleared from PCI_COMMAND, which is what we want. But when we get back to
    e1000_test_msi(), the INTX_DISABLE bit gets inadvertently re-set because
    of the attempt by e1000_test_msi() to re-enable SERR.
    
    The solution is to have e1000_test_msi() re-read the PCI_COMMAND bits as
    part of its attempt to re-enable SERR.
    
    During debugging/testing of this issue I found that not all the systems
    I ran on had the SERR bit set to begin with. And on some of the systems
    the same could be said for the INTX_DISABLE bit. Needless to say these
    latter systems didn't have a problem falling back to legacy INTx
    interrupts with the code as is.
    
    Signed-off-by: Dean Nelson <dnelson@redhat.com>
    Tested-by: Emil Tantilov <emil.s.tantilov@intel.com>
    Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Dean Nelson committed with gregkh Jun 29, 2010
  31. @gregkh

    xen: netfront: explicitly generate arp_notify event after migration.

    commit 5929706 upstream.
    
    Use newly introduced netif_notify_peers() method to ensure a gratuitous ARP is
    generated after a migration.
    
    Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
    Cc: Stephen Hemminger <shemminger@linux-foundation.org>
    Cc: Jeremy Fitzhardinge <jeremy@goop.org>
    Cc: David S. Miller <davem@davemloft.net>
    Cc: netdev@vger.kernel.org
    Cc: xen-devel@lists.xensource.com
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Ian Campbell committed with gregkh May 26, 2010
  32. @gregkh

    arp_notify: allow drivers to explicitly request a notification event.

    commit 06c4648 upstream.
    
    Currently such notifications are only generated when the device comes up or the
    address changes. However one use case for these notifications is to enable
    faster network recovery after a virtual machine migration (by causing switches
    to relearn their MAC tables). A migration appears to the network stack as a
    temporary loss of carrier and therefore does not trigger either of the current
    conditions. Rather than adding carrier up as a trigger (which can cause issues
    when interfaces a flapping) simply add an interface which the driver can use
    to explicitly trigger the notification.
    
    Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
    Cc: Stephen Hemminger <shemminger@linux-foundation.org>
    Cc: Jeremy Fitzhardinge <jeremy@goop.org>
    Cc: David S. Miller <davem@davemloft.net>
    Cc: netdev@vger.kernel.org
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Ian Campbell committed with gregkh May 26, 2010
  33. @gregkh

    amd64_edac: Fix operator precendence error

    commit 962b70a upstream.
    
    The bitwise AND is of higher precedence, make that explicit.
    
    Signed-off-by: Borislav Petkov <borislav.petkov@amd.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Borislav Petkov committed with gregkh Aug 3, 2010
  34. @gregkh

    amd64_edac: Correct scrub rate setting

    commit bc57117 upstream.
    
    Exit early when setting scrub rate on unknown/unsupported families.
    
    Signed-off-by: Borislav Petkov <borislav.petkov@amd.com>
    Acked-by: Doug Thompson <dougthompson@xmission.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Borislav Petkov committed with gregkh May 21, 2010
  35. @gregkh

    amd64_edac: Fix DCT base address selector

    commit 9975a5f upstream.
    
    The correct check is to verify whether in high range we're below 4GB
    and not to extract the DctSelBaseAddr again. See "2.8.5 Routing DRAM
    Requests" in the F10h BKDG.
    
    Signed-off-by: Borislav Petkov <borislav.petkov@amd.com>
    Acked-by: Doug Thompson <dougthompson@xmission.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Borislav Petkov committed with gregkh Mar 8, 2010