Alucard updated his HOTPLUG driver, pulled full updates, TNX @Alucard24
Revert "ARM: 7605/1: vmlinux.lds: Move .notes section next to the rodata"

This reverts commit 84fe6520046138974ad6340f941e0f3c303dd744.
Revert "ARM: 7568/1: Sort exception table at compile time"

This reverts commit 06839a47a277c7fdda65ddf90f13aaa269609ef0.
Revert "ARM: vmlinux.lds: use _text and _stext the same way as x86"

This reverts commit 12a4b6f2ba488cb53c45f06587d30b5c5f71b070.
Revert "ARM: vmlinux.lds: move init sections between text and data sections"

This reverts commit 6e930772262f16a8bc4df5f3cc7c11fa1c61b2b4.
Revert " ARM: vmlinux.lds: move discarded sections to beginning"

This reverts commit 7f613677c2e1617e8b8c528f14bd707d3a264c06.
Revert "ARM: vmlinux.lds: rearrange .init output section"

This reverts commit cadfaffc086c4307c8c42771a65aea5f7ac8e1f7.
Revert "ARM: vmlinux.lds: remove .rodata/.rodata1 from main .text segment"

This reverts commit 83b15d855d137203c049e36573e3cdb4d902f64c.
Config update
Merge branch 'sched-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip

Pull scheduler fixes from Ingo Molnar:
 "Misc fixes"

* 'sched-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
  sched: Fix comment for sched_info_depart
  sched/Documentation: Update sched-design-CFS.txt documentation
  sched/debug: Take PID namespace into account
  sched/fair: Fix small race where child->se.parent,cfs_rq might point to invalid ones
Merge branch 'timers-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip

Pull timer fix from Ingo Molnar:
 "An NTP related lockup fix"

* 'timers-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
  timekeeping: Fix HRTICK related deadlock from ntp lock changes
Added SuperSu 1.65 by Chainfire to kernel ZIP for installing on 4.3
Documentation + CREDITS + MAINTAINERS update from 3.12.rc1
Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs

Pull vfs fixes from Al Viro:
 "atomic_open-related fixes (Miklos' series, with EEXIST-related parts
  replaced with fix in fs/namei.c:atomic_open() instead of messing with
  the instances) + race fix in autofs + leak on failure exit in 9p"

* 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs:
  9p: don't forget to destroy inode cache if fscache registration fails
  atomic_open: take care of EEXIST in no-open case with O_CREAT|O_EXCL in fs/namei.c
  vfs: don't set FILE_CREATED before calling ->atomic_open()
  nfs: set FILE_CREATED
  gfs2: set FILE_CREATED
  cifs: fix filp leak in cifs_atomic_open()
  vfs: improve i_op->atomic_open() documentation
  autofs4: close the races around autofs4_notify_daemon()
fs/sync: Make sync() satisfy many requests with one invocation

Dave Jones reported RCU stalls, overly long hrtimer interrupts, and
amazingly long NMI handlers from a trinity-induced workload involving
lots of concurrent sync() calls (https://lkml.org/lkml/2013/7/23/369).
There are any number of things that one might do to make sync() behave
better under high levels of contention, but it is also the case that
multiple concurrent sync() system calls can be satisfied by a single
sys_sync() invocation.

Given that this situation is reminiscent of rcu_barrier(), this commit
applies the rcu_barrier() approach to sys_sync().  This approach uses
a global mutex and a sequence counter.  The mutex is held across the
sync() operation, which eliminates contention between concurrent sync()
operations.  The counter is incremented at the beginning and end of
each sync() operation, so that it is odd while a sync() operation is in
progress and even otherwise, just like sequence locks.

The code that used to be in sys_sync() is now in do_sync(), and sys_sync()
now handles the concurrency.  The sys_sync() function first takes a
snapshot of the counter, then acquires the mutex, and then takes another
snapshot of the counter.  If the values of the two snapshots indicate that
a full do_sync() executed during the mutex acquisition, the sys_sync()
function releases the mutex and returns ("Our work is done!").  Otherwise,
sys_sync() increments the counter, invokes do_sync(), and increments
the counter again.

This approach allows a single call to do_sync() to satisfy an arbitrarily
large number of sync() system calls, which should eliminate issues due
to large numbers of concurrent invocations of the sync() system call.

Changes since v1 (https://lkml.org/lkml/2013/7/24/683):

o	Add a pair of memory barriers to keep the increments from
	bleeding into the do_sync() code.  (The failure probability
	is insanely low, but when you have several hundred million
	devices running Linux, you can expect several hundred instances
	of one-in-a-million failures.)

o	Actually CC some people who have experience in this area.

Reported-by: Dave Jones <davej@redhat.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Jan Kara <jack@suse.cz>
Cc: Curt Wohlgemuth <curtw@google.com>
Cc: Jens Axboe <jaxboe@fusionio.com>
Cc: linux-fsdevel@vger.kernel.org

Signed-off-by: Paul Reioux <reioux@gmail.com>
Added NOTE to fs/sync.c after custom patch

https://github.com/dorimanx/Dorimanx-SG2-I9100-Kernel/commit/f7f90fe109ae4b44f4705a5be6961a2ce2301f0a
Removing scaling_governor_all_cpus as we cant use that on SG2 CPU
Deleted SCARY CPU GOV from system. it's was bugged and unstable.
Updated all UNUSED ARCH Trees from 3.12.rc1 to be in SYNC and optimized!

Some changes to way our ARCH is build.
Remove CPU counters. waste of power. useless for every one.