* Fix FSID of rootfs being 0

For st_dev in struct stat, the value 0 is
  an error. Make sure rootfs has value 1.

  This fixes the coreutils cp -ax issue (although that
  code has already been improved in coreutils, too) and
  somewhat fixes the switch_root problem in util-linux.
  It is still possible that rootfs gets an FSID >1 in
  future versions, so util-linux still needs to be fixed.

  This is unrelated to the mount id issue in
  /proc/*/mountinfo - the mount id may still be
  zero.

* Revert a patch that always enables autosuspend on intel bluetoothh

  xhci still sucks and breaks this. I am reverting this
  commit for reasons that are in no way selfish.

PKGBUILD

@@ -5,7 +5,7 @@ pkgbase=linux               # Build stock -ARCH kernel
 #pkgbase=linux-custom       # Build kernel with a different name
 _srcname=linux-3.14
 pkgver=3.14
-pkgrel=2
+pkgrel=3
 arch=('i686' 'x86_64')
 url="http://www.kernel.org/"
 license=('GPL2')
@@ -22,16 +22,20 @@ source=("https://www.kernel.org/pub/linux/kernel/v3.x/${_srcname}.tar.xz"
         '0002-module-allow-multiple-calls-to-MODULE_DEVICE_TABLE-p.patch'
         '0003-module-remove-MODULE_GENERIC_TABLE.patch'
         '0004-Revert-syscalls.h-use-gcc-alias-instead-of-assembler.patch'
+        '0005-fs-Don-t-return-0-from-get_anon_bdev.patch'
+        '0006-Revert-Bluetooth-Enable-autosuspend-for-Intel-Blueto.patch'
         )
 sha256sums=('61558aa490855f42b6340d1a1596be47454909629327c49a5e4e10268065dffa'
             '91b05561c96e09c8c3a4ea05fdab0745f578c4bb879feae25f552306bbe6522a'
             '00da25459826be1dced644c2215dfe2a6da53168d92aea79467c490aec4cbcae'
             'f0d90e756f14533ee67afda280500511a62465b4f76adcc5effa95a40045179c'
             'faced4eb4c47c4eb1a9ee8a5bf8a7c4b49d6b4d78efbe426e410730e6267d182'
-            '29a958c37e1fb04c49b1cc3be4f38b53ffdeef61ab049865209f6b77817302d0'
-            'd8db3b235d871d2b27986d3cb73a57b1d33fed52196a4b608152498a57e93838'
-            'eb9a773b7b978bc508e8459ef835ff2cb8a41bb235caff1c18c5b718d7ce902c'
-            '4edd92642d710d8a351dd2acce36d412eccbf60380f9d0368ec315acb49ad704')
+            'ad22f6e1a2869730828ddaf93da8b8a748421b7afdd34e1213566985fe7b01dd'
+            '29e612a8dda2b2b8af116c16b546a0e1d159f249bfd9628d640cad0f61f0cc4f'
+            '555133445de48e781ced3a450bcdf9bfbe4d66b118bbd5b28fea789fa023dd66'
+            'dc1eca93dad93c9c015332d188f5a69508c2077536b8be653d2ff45f1b034941'
+            '1f572e748d96403218e846ec469474f557f04d2f5ff137dd2a31fffa193f760e'
+            'a413700adf3b45b7d3c18d2ffed390b9e5769cb361a9a0530f98bfff29fd0aef')
 
 _kernelname=${pkgbase#linux}
 
@@ -60,6 +64,15 @@ prepare() {
   # For details, see https://lkml.org/lkml/2014/1/26/22
   patch -p1 -i "${srcdir}/0004-Revert-syscalls.h-use-gcc-alias-instead-of-assembler.patch"
 
+  # Fix various bugs caused by rootfs having FSID 0
+  # See http://www.spinics.net/lists/kernel/msg1716924.html
+  patch -p1 -i "${srcdir}/0005-fs-Don-t-return-0-from-get_anon_bdev.patch"
+
+  # Disable usb autosuspend for intel btusb
+  # See http://www.spinics.net/lists/kernel/msg1716461.html
+  # Until a solution is found, make sure the driver leaves autosuspend alone
+  patch -p1 -i "${srcdir}/0006-Revert-Bluetooth-Enable-autosuspend-for-Intel-Blueto.patch"
+
   if [ "${CARCH}" = "x86_64" ]; then
     cat "${srcdir}/config.x86_64" > ./.config
   else