add local version
use gzip instead
Enable camera debugging
Typo fix

Remove a b - thanks to papi92 for noticing this!
Revert change
config rmnet_usb
Subject: msm: camera: Add support for multiple SOF events.

Multiple SOF events are required, when running multiple HW streams on
a single VFE, and the user space needs to distinguish between
different SOFs in the different streams.  Such situation can occur,
when we have one or more RDI streams in parallel with a PIX stream.

Change-Id: Id4d03ca8d65d60ccbbb8949311a31607eb7417fe
Signed-off-by: Vladislav Hristov <vhrist@codeaurora.org>
Revert "Subject: msm: camera: Add support for multiple SOF events."

This reverts commit 164e9eb5afc2cdd16bae726a95b1602c511e4089.
msm: Create shadow files under /sys/kernel/ipv4

The TCP delayed ack parameters can be configured from user space application which runs with non-root credentials and does not have direct write access to /proc entries. This commit creates shadow files under /sys/kernel/ipv4 which maps to /proc/sys/net/ipv4. CRs-Fixed: 628139 Change-Id: If9f5e8f1f5f31c39090555b7b0c40efcdf6ccd08 Signed-off-by: Ravi Joshi <ravij@codeaurora.org>
add klte_eur_defconfig
update klte_eur_defconfig
revert

 msm: Create shadow files under /sys/kernel/ipv4

The TCP delayed ack parameters can be configured from user space application which runs with non-root credentials and does not have direct write access to /proc entries. This commit creates shadow files under /sys/kernel/ipv4 which maps to /proc/sys/net/ipv4. CRs-Fixed: 628139 Change-Id: If9f5e8f1f5f31c39090555b7b0c40efcdf6ccd08 Signed-off-by: Ravi Joshi <ravij@codeaurora.org>
Disable TACTILE_ASSIST for fixing vibrator
Disable TACTILE_ASSIST for fixing vibrator
Disable TACTILE_ASSIST for fixing vibrator
last commit for mtp fix
Merge pull request #1 from elelinux/cm-11.0

Pull MTP back to garwynn
msm_camera_qup_i2c_txdata() is not returning proper value.
Due to which session tear down is not happening properly
in case of i2c failure.
CRs-Fixed: 640328

Change-Id: Iac8be9d4755f807b45a6ede4f660b52cb88aedd4
Signed-off-by: Vivek Veenam <vveenam@codeaurora.org>
From 726d5b7b19f4b1c6c3ef9f2c6bc4c261563cca8c Mon Sep 17 00:00:00 2001
From: Vinay Kalia <vkalia@codeaurora.org>
Date: Fri, 17 Jan 2014 13:59:05 -0800
Subject: [PATCH] [media] v4l2-ioctl.c: handle PREPARE_BUF like QUERYBUF

The core code for PREPARE_BUF didn't take the multiplanar case into account,
which might cause page faults. Handle PREPARE_BUF just like QUERYBUF and
QBUF/DQBUF.

Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Git-commit: 96b1a70226cd43f69c63a7ba2a769bece08cf64e
Git-repo:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git

Change-Id: Ica94027b4189627b3e8e76e40e9fc1a6f71932cb
Signed-off-by: Vinay Kalia <vkalia@codeaurora.org>
futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr == uaddr2 in futex_requeue(..., requeue_pi=1)

If uaddr == uaddr2, then we have broken the rule of only requeueing
from a non-pi futex to a pi futex with this call. If we attempt this,
then dangling pointers may be left for rt_waiter resulting in an
exploitable condition.

This change brings futex_requeue() into line with
futex_wait_requeue_pi() which performs the same check as per commit
6f7b0a2a5 (futex: Forbid uaddr == uaddr2 in futex_wait_requeue_pi())

[ tglx: Compare the resulting keys as well, as uaddrs might be
  	different depending on the mapping ]

Fixes CVE-2014-3153.

Change-Id: I6bfa0943ee54d6331e6faa7779d621f9cf19fe52
Reported-by: Pinkie Pie
Signed-off-by: Will Drewry <wad@chromium.org>
Signed-off-by: Kees Cook <keescook@chromium.org>
Cc: stable@vger.kernel.org
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
futex: Validate atomic acquisition in futex_lock_pi_atomic()

We need to protect the atomic acquisition in the kernel against rogue
user space which sets the user space futex to 0, so the kernel side
acquisition succeeds while there is existing state in the kernel
associated to the real owner.

Verify whether the futex has waiters associated with kernel state. If
it has, return -EINVAL. The state is corrupted already, so no point in
cleaning it up. Subsequent calls will fail as well. Not our problem.

[ tglx: Use futex_top_waiter() and explain why we do not need to try
  	restoring the already corrupted user space state. ]

Change-Id: Ifca31cf91f32a408171a01b8db1e49c14411a776
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Cc: Kees Cook <keescook@chromium.org>
Cc: Will Drewry <wad@chromium.org>
Cc: stable@vger.kernel.org
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>