cpufreq:Few updates to Conservative Governor

Updates came from AOSP source..

Seriously..Thank you!! lolz..(**sniff**)

Signed-off-by: zeroblade1984 <zeroblade1984@gmail.com>
wireless:BCMDHD fixes from CAF

This is a port of a fix from CAF source tree for BCMDHD wireless LAN driver.

Reference of the commit came from here: https://www.codeaurora.org/cgit/quic/la/kernel/msm/commit/?h=aosp-common/android-3.4&id=acddfe97de2ccf22d05ccc944469a16e7308ac7a

Credits due to original author:
Signed-off-by: Ritter Yeh <ryeh@broadcom.com>
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>

Now for the shitty comment:
Once again if you find/dig interest in cooking this up hit the jackpot.. :D
I'm no RC or anything with title to proove anything on XDA all I have to do is just COMPLY..COMPLY and COMPLY.. >:D

Signed-off-by: zeroblade1984 <zeroblade1984@gmail.com>
wireless:Remove debugging

I never thought this would be of use here from the Galaxy Note2/S3 Wifi driver tweaks.

Signed-off-by: zeroblade1984 <zeroblade1984@gmail.com>
sched: Fix inaccurate accounting for real-time task

It is possible that rq->clock_task was not updated in put_prev_task()
in which case we can potentially overcharge a real-time task for time
it did not run. This is because clock_task could be stale and not
represent the exact time real-time task started running.

Fix this by forcing update of rq->clock_task when real-time task
starts running.

Signed-off-by: Srivatsa Vaddagiri <vatsa@codeaurora.org>
block: do not notify urgent request, when flush with data in flight

MMC device driver implements URGENT request execution with priority
(using stop flow), as a result currently running (and prepared) request
may be reinserted back into I/O scheduler. This will break block layer
logic of flushes (flush request should not be inserted into I/O scheduler).

Block layer flush machinery keep q->flush_data_in_flight list updated with
started but not completed flush requests with data (REQ_FUA).

This change will not notify underling block device driver about pending
urgent request during flushes in flight.

Change-Id: I8b654925a3c989250fcb8f4f7c998795fb203923
Signed-off-by: Konstantin Dorfman <kdorfman@codeaurora.org>
Signed-off-by: Tatyana Brokhman <tlinder@codeaurora.org>
net: loopback: set default mtu to 64K

loopback current mtu of 16436 bytes allows no more than 3 MSS TCP
segments per frame, or 48 Kbytes. Changing mtu to 64K allows TCP
stack to build large frames and significantly reduces stack overhead.

Performance boost on bulk TCP transferts can be up to 30 %, partly
because we now have one ACK message for two 64KB segments, and a lower
probability of hitting /proc/sys/net/ipv4/tcp_reordering default limit.

Signed-off-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
ext4: limit the number of error prints

Use printk_ratelimit instead so as to avoid large number of prints
from the EXT4 in case of error.

Signed-off-by: Tatyana Brokhman <tlinder@codeaurora.org>
Signed-off-by: Subhash Jadavani <subhashj@codeaurora.org>
Signed-off-by: Sahitya Tummala <stummala@codeaurora.org>
Revert "Patch:Linux 3.4.11-3.4.105"

I don't want to pay any tribute or shit to anybody that thinks low of me..thats it..I'm reverting this as my kernel is still best even without it and the fact that HTC or Google could have updated their own kernel bases to the latest and cutting edge Linux version..but they did not..we are running a smart phone and not a desktop here..

This reverts commit 761da6a2a8789ced1a0b72b5315475b2da6ebaff.