compat-drivers: refresh patches for v3.8.2

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: fix processing pending-stable patches

Upstream commit 919b760cab4a22092987a5653df4b67db65757f3

After we got DRM subsystem support the patches for each
subsystem were separated. Stable patches then need to
be broken down as well. This fixes this and restores
the behaviour allowing us to make -s releases.

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: fix removal of tmp pending-stable files

Upstream commit 74b6184ee49bc721932513dd7f1c2cd0216ecc59

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: fix copying of pending-stable patches

Upstream commit 73029dc4420a640067a810f66f7e0d9a14611166

This correctly copies the pending-stable patches for each
subsystem. When running ./scripts/admin-update.sh -s
we will now stats pending-stable for each subsystem:

compat-drivers code metrics

   1320032 - Total upstream lines of code being pulled

   network
   ----------------------------------------
      3105 - backport code changes
      2602 - backport code additions
       503 - backport code deletions
     15003 - backport from compat module
     18108 - total backport code
    1.3718 - % of code consists of backport work
       192 - Code changes brought in from pending-stable
       124 - Code additions brought in from pending-stable
        68 - Code deletions brought in from pending-stable
    0.0145 - % of code being cherry picked from pending-stable

   drm
   ----------------------------------------
       437 - backport code changes
       293 - backport code additions
       144 - backport code deletions
     15003 - backport from compat module
     15440 - total backport code
    1.1697 - % of code consists of backport work

Base tree: linux-stable.git
Base tree version: v3.9-rc1
compat.git: compat-v3.9-rc1-1
compat-drivers release: compat-drivers-v3.9-rc1-2-4-g9f5e67f-s
Code metrics archive: http://bit.ly/H6BTF7

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: skip already appplied patches

Upstream commit 4a1a94f933b24e161ab1ca0a51f67698aa680bba

GNU Patch does not yet support giving a different
error return value for patches detected as reversed or
already applied. We can add that support but for now
we distinguish this by grep'ing the results. We nuke
already applied patches, this typically would come from
linux-next, on linux-stable branches given that there is
no linearity between the two.

To support this change however it means we now have
the double amount of time it takes to apply patches
given that we now need a dry run first. The algorithm
for checking if a patch is reversed only works by
analyzing the first hunk of a patch though so perhaps
what we need on GNU Patch is a check for asking if
a patch is reversed, that would not cause much
overhead here, it would just dry run on the first
hunk by reducing the search space considerably.

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: skip pending stable mac80211 patch

Skip this patch given that the context it is trying to
fix is not part of v3.8 series.

commit 5b36ebd8249f403c7edf7cf68d68e9a0d0f55243
Author: Johannes Berg <johannes.berg@intel.com>
Date:   Wed Feb 13 14:21:45 2013 +0100

    mac80211: always unblock CSA queue stop when disconnecting

    In some cases when disconnecting after (or during?) CSA
    the queues might not recover, and then the only way to
    recover is reloading the module.

    Fix this by always unblocking the queue CSA reason when
    disconnecting.

    Cc: stable@vger.kernel.org
    Reported-by: Jan-Michael Brummer <jan.brummer@tabos.org>
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: backport rt2x00 pending-stable fix

The patch below required some manual editing of the first hunk
given that the original mesh support patch failed to add support
for mesh in one line, we just add it here.

commit 6ef9e2f6d12ce9e2120916804d2ddd46b954a70b
Author: Felix Fietkau <nbd@openwrt.org>
Date:   Tue Feb 26 16:09:55 2013 +0100

    rt2x00: error in configurations with mesh support disabled

    If CONFIG_MAC80211_MESH is not set, cfg80211 will now allow advertising
    interface combinations with NL80211_IFTYPE_MESH_POINT present.
    Add appropriate ifdefs to avoid running into errors.

    Cc: stable@vger.kernel.org
    Signed-off-by: Felix Fietkau <nbd@openwrt.org>
    Acked-by: Gertjan van Wingerde <gwingerde@gmail.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: skip DRM udl stable fix

The following patches is irrelevant to v3.8 as the DRM
udl driver is not present on v3.8.

commit bcb39af4486be07e896fc374a2336bad3104ae0a
Author: Dave Airlie <airlied@redhat.com>
Date:   Thu Feb 7 11:19:15 2013 +1000

    drm/udl: make usage as a console safer

    Okay you don't really want to use udl devices as your console, but if
    you are unlucky enough to do so, you run into a lot of schedule while atomic
    due to printk being called from all sorts of funky places. So check if we
    are in an atomic context, and queue the damage for later, the next printk
    should cause it to appear. This isn't ideal, but it is simple, and seems to
    work okay in my testing here.

    (dirty area idea came from xenfb)

    fixes a bunch of sleeping while atomic issues running fbcon on udl devices.

    Cc: stable@vger.kernel.org
    Signed-off-by: Dave Airlie <airlied@redhat.com>

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: skip another DRM udl stable fix

This is also irrelevant for v3.8

commit 677d23b70bf949f75746c80cbae92c233c6b5e2a
Author: Dave Airlie <airlied@redhat.com>
Date:   Thu Feb 7 12:30:25 2013 +1000

    drm/udl: disable fb_defio by default

    There seems to be a bad interaction between gem/shmem and defio on top,
    I get list corruption on the page lru in the shmem code.

    Turn it off for now until we get some more digging done.

    Cc: stable@vger.kernel.org
    Signed-off-by: Dave Airlie <airlied@redhat.com>

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: ignore drm i915 brightness quirk stable fix

This is already present on v3.8 but GNU Patch can't tell
its a reversed patch because the context of the patch
differs from the code. Just add it to the ignore list.

commit ac4199e0f047546aa40172785e26c82b54bbe811
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Fri Feb 15 18:35:30 2013 +0100

    drm/i915: inverted brightness quirk for Acer Aspire 4736Z

    Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=53881
    Cc: stable@vger.kernel.org
    Cc: Jani Nikula <jani.nikula@intel.com>
    Tested-by: Jani Monoses <jani@ubuntu.com>
    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: add pending-stable patches

This is against next-20130307

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: update genlog for 3.8

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: fix commend for genlog

Upstream commit c67959a0021c65b195e746e7f7891f19a4f07b0c

The genlog script was giving the incorrect command
we use to generate the log for the kernel, fix this.

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: refresh patches for v3.8.3

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: refresh unified patches for v3.8.3

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: refresh pending-stable patches for v3.8.3

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: add linux-next-pending patches

We suck these out from the linux-wireless mailing
list. We carry three:

commit d02bdeb7e4a5ca55f02a135329f1d790ec469712
Author: Felix Fietkau <nbd@openwrt.org>
Date:   Fri Mar 15 11:39:05 2013 -0700

    ath9k_hw: revert chainmask to user configuration after calibration

    The commit 'ath9k_hw: fix calibration issues on chainmask that don't
    include chain 0' changed the hardware chainmask to the chip chainmask
    for the duration of the calibration, but the revert to user
    configuration in the reset path runs too early.

    That causes some issues with limiting the number of antennas (including
    spurious failure in hardware-generated packets).

    Fix this by reverting the chainmask after the essential parts of the
    calibration that need the workaround, and before NF calibration is run.

    Backported to v3.8 by Luis.

    Signed-off-by: Felix Fietkau <nbd@openwrt.org>
    Reported-by: Wojciech Dubowik <Wojciech.Dubowik@neratec.com>
    Tested-by: Wojciech Dubowik <Wojciech.Dubowik@neratec.com>
    Cc: stable@vger.kernel.org

commit a1ec3d31cd6a3b64ee5506fc11e14b48c4e05fa6
Author: Felix Fietkau <nbd@openwrt.org>
Date:   Fri Mar 15 16:18:44 2013 +0100

    ath9k: limit tx path hang check to normal data queues

    The beacon and multicast-buffer queues are managed by the beacon
    tasklet, and the generic tx path hang check does not help in any way
    here. Running it on those queues anyway can introduce some race
    conditions leading to unnecessary chip resets.

    Cc: stable@vger.kernel.org
    Signed-off-by: Felix Fietkau <nbd@openwrt.org>

commit 102a727c8b8d9c8aa2e4526a02c784326b63d639
Author: Johannes Berg <johannes.berg@intel.com>
Date:   Wed Mar 6 23:19:26 2013 +0100

    mac80211: always synchronize_net() during station removal

    If there are keys left during station removal, then a
    synchronize_net() will be done (for each key, I have a
    patch to address this for 3.10), otherwise it won't be
    done at all which causes issues because the station
    could be used for TX while it's being removed from the
    driver -- that might confuse the driver.

    Fix this by always doing synchronize_net() if no key
    was present any more.

    Cc: stable@vger.kernel.org
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: add first set of linux-next-cherry-picks patches

We cherry pick only two so far, these were cherry-picked
from next-20130315.

commit a98285986afd39658978fe1fc1be8160cf877f61
Author: Sujith Manoharan <c_manoha@qca.qualcomm.com>
Date:   Mon Mar 4 12:42:55 2013 +0530

    ath9k_hw: Fix fixed antenna for AR9462

    When the RX chainmask is set to 0x2 for AR9462, certain values
    from chain1 have to be programmed for chain0 also.

    Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>

commit 5ce7f6ccc88b3acfa652fa4eb1ad1b8f9038681f
Author: Sujith Manoharan <c_manoha@qca.qualcomm.com>
Date:   Mon Mar 4 12:42:54 2013 +0530

    ath9k_hw: Update initvals for AR9462

    Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: update genlog-3.8 for v3.8.3

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>