commit 5c68732e7504d2e3745c272979c2eeddd7661e5a
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Sat Sep 14 07:07:01 2013 -0700

    Linux 3.11.1

commit ae7ab51a0ad97b41a3e173a52af033dd9e5eb118
Author: Bing Zhao <bzhao@marvell.com>
Date:   Mon Aug 19 16:10:21 2013 -0700

    mwifiex: do not create AP and P2P interfaces upon driver loading
    
    commit 1211c961170cedb21c30d5bb7e2033c8720b38db upstream.
    
    Bug 60747 - 1286:2044 [Microsoft Surface Pro]
        Marvell 88W8797 wifi show 3 interface under network
    https://bugzilla.kernel.org/show_bug.cgi?id=60747
    
    This issue was also reported previously by OLPC and some folks from
    the community.
    
    There are 3 network interfaces with different types being created
    when mwifiex driver is loaded:
    
    1. mlan0 (infra. STA)
    2. uap0 (AP)
    3. p2p0 (P2P_CLIENT)
    
    The Network Manager attempts to use all 3 interfaces above without
    filtering the managed interface type. As the result, 3 identical
    interfaces are displayed under network manager. If user happens to
    click on an entry under which its interface is uap0 or p2p0, the
    association will fail.
    
    Work around it by removing the creation of AP and P2P interfaces
    at driver loading time. These interfaces can be added with 'iw' or
    other applications manually when they are needed.
    
    Signed-off-by: Bing Zhao <bzhao@marvell.com>
    Signed-off-by: Avinash Patil <patila@marvell.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit cc798574e811d922e935328276414f5cca58bfe8
Author: Sangjung Woo <sangjung.woo@samsung.com>
Date:   Wed Sep 11 14:24:21 2013 -0700

    drivers/rtc/rtc-max77686.c: Fix wrong register
    
    commit 1748cbf7f7c464593232cde914f5a103181a83b5 upstream.
    
    Fix a read of the wrong register when checking whether the RTC timer has
    reached the alarm time.
    
    Signed-off-by: Sangjung Woo <sangjung.woo@samsung.com>
    Signed-off-by: Myugnjoo Ham <myungjoo.ham@samsung.com>
    Reviewed-by: Jonghwa Lee <jonghwa3.lee@samsung.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Jonghwan Choi <jhbird.choi@samsung.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 34bf8c60e35037c21db3a52a2da7ea557dfd9ea6
Author: John Haxby <john.haxby@oracle.com>
Date:   Wed Aug 14 16:23:18 2013 +0100

    crypto: xor - Check for osxsave as well as avx in crypto/xor
    
    commit edb6f29464afc65fc73767540b854abf63ae7144 upstream.
    
    This affects xen pv guests with sufficiently old versions of xen and
    sufficiently new hardware.  On such a system, a guest with a btrfs
    root won't even boot.
    
    Signed-off-by: John Haxby <john.haxby@oracle.com>
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
    Reported-by: Michael Marineau <michael.marineau@coreos.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 682903751a46cb1704f3f29d7f0c7c408d5b8da5
Author: Fabio Estevam <fabio.estevam@freescale.com>
Date:   Fri Jun 28 13:55:27 2013 -0300

    imx-drm: imx-drm-core: Export imx_drm_encoder_get_mux_id
    
    commit ea8d15832016b0d07a8121159904e6b1d21b5b8b upstream.
    
    When building imx_v6_v7_defconfig with imx-drm drivers selected as modules, we
    get the following build error:
    
    ERROR: "imx_drm_encoder_get_mux_id" [drivers/staging/imx-drm/imx-ldb.ko] undefined!
    
    Export the required function to avoid this problem.
    
    Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
    Acked-by: Sascha Hauer <s.hauer@pengutronix.de>
    Acked-by: Philipp Zabel <p.zabel@pengutronix.de>
    Cc: Guenter Roeck <linux@roeck-us.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit ec6ad8831fe8562e774ad9d6e0f191f48798c5d3
Author: Fabio Estevam <fabio.estevam@freescale.com>
Date:   Mon Jul 29 18:37:32 2013 -0300

    ASoC: fsl: Fix module build
    
    commit 3f1a91aa25579ba5e7268a47a73d2a83e4802c62 upstream.
    
    Building imx_v6_v7_defconfig with all audio drivers as modules results in
    the folowing build error:
    
    ERROR: "imx_pcm_fiq_init" [sound/soc/fsl/snd-soc-imx-ssi.ko] undefined!
    ERROR: "imx_pcm_dma_init" [sound/soc/fsl/snd-soc-imx-ssi.ko] undefined!
    ERROR: "imx_pcm_fiq_exit" [sound/soc/fsl/snd-soc-imx-ssi.ko] undefined!
    ERROR: "imx_pcm_dma_exit" [sound/soc/fsl/snd-soc-imx-ssi.ko] undefined!
    ERROR: "imx_pcm_dma_init" [sound/soc/fsl/snd-soc-fsl-ssi.ko] undefined!
    ERROR: "imx_pcm_dma_exit" [sound/soc/fsl/snd-soc-fsl-ssi.ko] undefined!
    
    Fix this by allowing SND_SOC_IMX_PCM_FIQ and SND_SOC_IMX_PCM_DMA to be also
    built as modules and by using 'IS_ENABLED' to cover the module case.
    
    Reported-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
    Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
    Acked-by: Shawn Guo <shawn.guo@linaro.org>
    Signed-off-by: Mark Brown <broonie@linaro.org>
    [Guenter Roeck: back-ported to 3.11]
    Signed-off-by: Guenter Roeck <linux@roeck-us.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 1a5d00e3fd43164493ddbd3e71d3ac16be3bd5e7
Author: Mark Rusk <Mark.Rusk@hp.com>
Date:   Wed Aug 14 15:30:01 2013 -0500

    drivers/misc/hpilo: Correct panic when an AUX iLO is detected
    
    commit eefbc594abbb1b7e6e7eeadb65ae7c7538474210 upstream.
    
     Using an uninitialized variable 'devnum' after 'goto out;' was causing
     panic.  Just go ahead and return, we need to ignore AUX iLO devs.
    
     Oops: 0002 [#1] SMP
       .
       .
       .
     RIP  [<ffffffffa033e270>] ilo_probe+0xec/0xe7c [hpilo]
    
    Signed-off-by: Mark Rusk <mark.rusk@hp.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit ae5a8bc479ef265c1cb56bcd32d33f7af38b35ca
Author: Lan Tianyu <tianyu.lan@intel.com>
Date:   Mon Aug 26 10:19:18 2013 +0800

    ACPI / EC: Add ASUSTEK L4R to quirk list in order to validate ECDT
    
    commit 524f42fab787a9510be826ce3d736b56d454ac6d upstream.
    
    The ECDT of ASUSTEK L4R doesn't provide correct command and data
    I/O ports.  The DSDT provides the correct information instead.
    
    For this reason, add this machine to quirk list for ECDT validation
    and use the EC information from the DSDT.
    
    [rjw: Changelog]
    References: https://bugzilla.kernel.org/show_bug.cgi?id=60765
    Reported-and-tested-by: Daniele Esposti <expo@expobrain.net>
    Signed-off-by: Lan Tianyu <tianyu.lan@intel.com>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit a493880d86c8bf516c63a4f3a50b39832f35acc1
Author: K. Y. Srinivasan <kys@microsoft.com>
Date:   Mon Aug 26 14:08:58 2013 -0700

    Drivers: hv: vmbus: Fix a bug in the handling of channel offers
    
    commit 42dceebe34600b2d02a38baa3e869009ba3d14c7 upstream.
    
    The channel state should be correctly set before registering the device. In the current
    code the driver probe would fail for channels that have been rescinded and subsequently
    re-offered. Fix the bug.
    
    Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 5d6d1d5cc50b4226d63303f061ebf2662395b627
Author: Wei Hu <wei@aristanetworks.com>
Date:   Fri Aug 23 13:14:03 2013 -0700

    hwmon: (k10temp) Add support for Fam16h (Kabini)
    
    commit 30b146d1cb5e7560192057098eb705118bd5511f upstream.
    
    The temperature reporting interface stays the same, so we just
    add the PCI-ID to the list.
    
    Verified on AMD Olive Hill.
    
    Signed-off-by: Wei Hu <wei@aristanetworks.com>
    Acked-by: Clemens Ladisch <clemens@ladisch.de>
    Signed-off-by: Guenter Roeck <linux@roeck-us.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit a14894e25d0c5c1871e4e8c52f3d54517f0e459b
Author: Graham Williams <gwilli@broadcom.com>
Date:   Wed Aug 28 16:36:14 2013 -0700

    usb: acm gadget: Null termintate strings table
    
    commit d257221854f0b34cca3247e6c45344d0470f7398 upstream.
    
    The gadget strings table should be null terminated.
    usb_gadget_get_string() loops through the table
    expecting a null at the end of the list.
    
    Signed-off-by: Graham Williams <gwilli@broadcom.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit a091ec1987ef9e73d8cb970fe885af1483e6e4c7
Author: Tomas Winkler <tomas.winkler@intel.com>
Date:   Tue Jul 30 14:11:51 2013 +0300

    mei: me: fix hardware reset flow
    
    commit ff96066e3171acdea356b331163495957cb833d0 upstream.
    
    Both H_IS and H_IE needs to be set to receive H_RDY
    interrupt
    
    1. Assert H_IS to clear the interrupts during hw reset
    and use mei_me_reg_write instead of mei_hcsr_set as the later
    strips down the H_IS
    
    2. fix interrupt disablement embarrassing typo
      hcsr |= ~H_IE -> hcsr &= ~H_IE;
    this will remove the unwanted interrupt on power down
    
    3. remove useless debug print outs
    
    Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
    Cc: Shuah Khan <shuah.kh@samsung.com>
    Cc: Konstantin Khlebnikov <khlebnikov@openvz.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit a8f55b8e314fdc26deb92a1108ebfd413cae9dde
Author: Nicholas Bellinger <nab@linux-iscsi.org>
Date:   Sat Aug 31 15:12:01 2013 -0700

    target: Fix se_cmd->state_list leak regression during WRITE failure
    
    commit c130480b129fbfd7932ad7af3f4ffcea630b027f upstream.
    
    This patch addresses a v3.11 specific regression where se_cmd->state_list
    was being leaked during a fabric WRITE failure, when the fabric releases
    an associated se_cmd descriptor before I/O submission occurs, and normal
    fast path callbacks have a chance to call target_remove_from_state_list().
    
    It was manifesting with Poison overwritten messages with iscsi-target
    once an ImmediateData payload CRC32C failure occured.
    
    This bug was originally introduced during v3.11-rc1 with the following
    commit:
    
    commit 0b66818ac6de67a6125ae203272fb76e79b3a20f
    Author: Nicholas Bellinger <nab@linux-iscsi.org>
    Date:   Thu Jun 6 01:36:41 2013 -0700
    
        target: Drop unnecessary CMD_T_DEV_ACTIVE check from transport_lun_remove_cmd
    
    Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 96dba890600864c6753c1db27bc46e4aa6a01f68
Author: Nicholas Bellinger <nab@linux-iscsi.org>
Date:   Fri Aug 23 22:28:56 2013 -0700

    iscsi-target: Fix potential NULL pointer in solicited NOPOUT reject
    
    commit 28aaa950320fc7b8df3f6d2d34fa7833391a9b72 upstream.
    
    This patch addresses a potential NULL pointer dereference regression in
    iscsit_setup_nop_out() code, specifically for two cases when a solicited
    NOPOUT triggers a ISCSI_REASON_PROTOCOL_ERROR reject to be generated.
    
    This is because iscsi_cmd is expected to be NULL for solicited NOPOUT
    case before iscsit_process_nop_out() locates the descriptor via TTT
    using iscsit_find_cmd_from_ttt().
    
    This regression was originally introduced in:
    
    commit ba159914086f06532079fc15141f46ffe7e04a41
    Author: Nicholas Bellinger <nab@linux-iscsi.org>
    Date:   Wed Jul 3 03:48:24 2013 -0700
    
        iscsi-target: Fix iscsit_add_reject* usage for iser
    
    Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit dd35452f39a61bd4264efa421b8ccc2623954700
Author: Nicholas Bellinger <nab@linux-iscsi.org>
Date:   Sun Aug 18 15:07:44 2013 -0700

    iscsi-target: Fix iscsit_transport reference leak during NP thread reset
    
    commit c9a03c12464c851e691e8d5b6c9deba779c512e0 upstream.
    
    This patch fixes a bug in __iscsi_target_login_thread() where an explicit
    network portal thread reset ends up leaking the iscsit_transport module
    reference, along with the associated iscsi_conn allocation.
    
    This manifests itself with iser-target where a NP reset causes the extra
    iscsit_transport reference to be taken in iscsit_conn_set_transport()
    during the reset, which prevents the ib_isert module from being unloaded
    after the NP thread shutdown has finished.
    
    Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit b26ae3b80f2bcac064962eea244617c4cad140bb
Author: Nicholas Bellinger <nab@linux-iscsi.org>
Date:   Thu Aug 22 00:05:45 2013 -0700

    iscsi-target: Fix ImmediateData=Yes failure regression in >= v3.10
    
    commit 9d86a2befceb06ee83c1a588915e6d6e0abef797 upstream.
    
    This patch addresses a regression bug within ImmediateData=Yes failure
    handling that ends up triggering an OOPs within >= v3.10 iscsi-target
    code.
    
    The problem occurs when iscsit_process_scsi_cmd() does the call to
    target_put_sess_cmd(), and once again in iscsit_get_immediate_data()
    that is triggered during two different cases:
    
     - When iscsit_sequence_cmd() returns CMDSN_LOWER_THAN_EXP, for which
       the descriptor state will already have been set to ISTATE_REMOVE
       by iscsit_sequence_cmd(), and
     - When iscsi_cmd->sense_reason is set, for which iscsit_execute_cmd()
       will have already called transport_send_check_condition_and_sense()
       to queue the exception response.
    
    It changes iscsit_process_scsi_cmd() to drop the early call, and makes
    iscsit_get_immediate_data() call target_put_sess_cmd() from a single
    location after dumping the immediate data for the failed command.
    
    The regression was initially introduced in commit:
    
    commit 561bf15892375597ee59d473a704a3e634c4f311
    Author: Nicholas Bellinger <nab@linux-iscsi.org>
    Date:   Wed Jul 3 03:58:58 2013 -0700
    
        iscsi-target: Fix iscsit_sequence_cmd reject handling for iser
    
    Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 3278d90c5828197f9e1ffcf4b93b7ef990752614
Author: Nicholas Bellinger <nab@linux-iscsi.org>
Date:   Wed Jul 24 16:15:08 2013 -0700

    target: Fix trailing ASCII space usage in INQUIRY vendor+model
    
    commit ee60bddba5a5f23e39598195d944aa0eb2d455e5 upstream.
    
    This patch fixes spc_emulate_inquiry_std() to add trailing ASCII
    spaces for INQUIRY vendor + model fields following SPC-4 text:
    
      "ASCII data fields described as being left-aligned shall have any
       unused bytes at the end of the field (i.e., highest offset) and
       the unused bytes shall be filled with ASCII space characters (20h)."
    
    This addresses a problem with Falconstor NSS multipathing.
    
    Reported-by: Tomas Molota <tomas.molota@lightstorm.sk>
    Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>