cpufreq: intelliactive: fix compiler warnings

Since sprintf(...) just return 1 (one character) in this case, ret should not changed. Just discarding the result of sprintf(...) leads to the result that the author wants.

drivers/cpufreq/cpufreq_intelliactive.c: In function 'show_target_loads':
drivers/cpufreq/cpufreq_intelliactive.c:867:6: warning: operation on 'ret' may be undefined [-Wsequence-point]
  ret += sprintf(buf + --ret, "\n");
      ^
drivers/cpufreq/cpufreq_intelliactive.c: In function 'show_above_hispeed_delay':
drivers/cpufreq/cpufreq_intelliactive.c:910:6: warning: operation on 'ret' may be undefined [-Wsequence-point]
  ret += sprintf(buf + --ret, "\n");
      ^

Inspired by commit 4a7cebd91f796fcb9d1e1e5723de27b75f1712d6 @ https://gitorious.org/linux-sunxi/linux-sunxi/
added CPU voltage VDD control (thanks to @Faux123)

Conflicts:
	arch/arm/configs/yuga_defconfig
	arch/arm/mach-msm/Kconfig
	drivers/cpufreq/cpufreq.c
arm: configs: enabled RTS write for yuga
added CPU freq governor wheatley (thanks to @Ezekeel)
arm: configs: enabled wheatley gov for yuga
unix: fix a race condition in unix_release()

As reported by Jan, and others over the past few years, there is a
race condition caused by unix_release setting the sock->sk pointer
to NULL before properly marking the socket as dead/orphaned.  This
can cause a problem with the LSM hook security_unix_may_send() if
there is another socket attempting to write to this partially
released socket in between when sock->sk is set to NULL and it is
marked as dead/orphaned.  This patch fixes this by only setting
sock->sk to NULL after the socket has been marked as dead; I also
take the opportunity to make unix_release_sock() a void function
as it only ever returned 0/success.

Dave, I think this one should go on the -stable pile.

Special thanks to Jan for coming up with a reproducer for this
problem.

CRs-Fixed: 660580
Change-Id: I0e39b84464cf3f4c9daf8677bba444d0d6d94825
Reported-by: Jan Stancek <jan.stancek@gmail.com>
Signed-off-by: Paul Moore <pmoore@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Git-commit: ded34e0fe8fe8c2d595bfa30626654e4b87621e0
Git-repo: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/
Signed-off-by: Vignesh Radhakrishnan <vigneshr@codeaurora.org>
USB: gadget: mtp: Fix hang in ioctl(MTP_RECEIVE_FILE) for WritePartialObject

In receive_file_work, we now queue reads with length rounded up to
max packet size rather than mtp_rx_req_len.
Otherwise the read request will never complete.

Signed-off-by: Mike Lockwood <lockwood@google.com>

Conflicts:
	drivers/usb/gadget/f_mtp.c
usb: gadget: Ignore the second set_config from the host

Some USB hosts may send SET_CONFIGURATION with same value twice.
The current code implementation of android_work() issues disconnect
event to userspace if SetConfiguration with non-zero value is sent
twice. The Userspace application may disconnect USB and it causes
fail to connect to the USB host.

Fix this by ignoring the second time SET_CONFIGURATION request
from the host only for the same configuration value twice.

CRs-Fixed: 661220
Change-Id: Iec8dd7824fa9f371ea147784cf9137aa88a7128e
Signed-off-by: ChandanaKishori Chiluveru <cchilu@codeaurora.org>
usb: android: Skip the work when set_config arrives with same value twice

Some USB hosts may send SET_CONFIGURATION with same value twice.
The current code implementation processing the 2nd set_config and
schedules the work. The android_work() issues disconnect event to
userspace if SetConfiguration with non-zero value is sent twice.
The userspace applications may disconnect the USB and the device
doesn't connect to the host.

Fix this by avoiding the android_work for the second time SET_CONFIGURATION
request when it receives SetConfiguration request with same configuration
value twice from the host.

CRs-Fixed: 661220
Change-Id: Ic450315a9067b9b679b4936480d125e4e4b7cdf7
Signed-off-by: ChandanaKishori Chiluveru <cchilu@codeaurora.org>

Conflicts:
	drivers/usb/gadget/android.c
Revert "usb: android: Skip the work when set_config arrives with same value twice"

This reverts commit 7a73a9ca4b0b30a6b2c466d79fc786adea058976.