Marking 9999 ebuild for sys-kernel/lakitu-kernel-4_19 as stable.

Change-Id: I0a5e3dab4b1dec21a1ff2f275418bf89b4450fcd
diff --git a/overlay-lakitu/sys-kernel/lakitu-kernel-4_19/lakitu-kernel-4_19-4.19.127-r538.ebuild b/overlay-lakitu/sys-kernel/lakitu-kernel-4_19/lakitu-kernel-4_19-4.19.127-r539.ebuild
similarity index 88%
rename from overlay-lakitu/sys-kernel/lakitu-kernel-4_19/lakitu-kernel-4_19-4.19.127-r538.ebuild
rename to overlay-lakitu/sys-kernel/lakitu-kernel-4_19/lakitu-kernel-4_19-4.19.127-r539.ebuild
index 864d3dd..4dd12c5 100644
--- a/overlay-lakitu/sys-kernel/lakitu-kernel-4_19/lakitu-kernel-4_19-4.19.127-r538.ebuild
+++ b/overlay-lakitu/sys-kernel/lakitu-kernel-4_19/lakitu-kernel-4_19-4.19.127-r539.ebuild
@@ -1,17 +1,12 @@
 # Copyright 2019 The Chromium OS Authors. All rights reserved.
 # Distributed under the terms of the GNU General Public License v2
 
-# Any changes submitted in the current ebuild needs to be duplicated in
-# `9999` ebuild as well.
-
 EAPI=6
 
-CROS_WORKON_REPO="https://cos.googlesource.com"
-CROS_WORKON_PROJECT="third_party/kernel"
-CROS_WORKON_EGIT_BRANCH="cos-4.19"
 CROS_WORKON_COMMIT="f8649a7408c63f53937e33b0e8379679b0434849"
+CROS_WORKON_TREE="1fa712dd5c6ce7f1be76a4137857ff44520b992a"
+CROS_WORKON_PROJECT="third_party/kernel"
 CROS_WORKON_LOCALNAME="kernel/v4.19"
-CROS_WORKON_BLACKLIST="1"
 
 CHROMEOS_KERNEL_CONFIG="${FILESDIR}/base.config"
 
@@ -21,7 +16,7 @@
 STRIP_MASK+=" /usr/src/${P}/build/vmlinux"
 STRIP_MASK+=" *.ko"
 
-DESCRIPTION="Chromium OS Linux Kernel 4.19"
+DESCRIPTION="COS Linux Kernel 4.19"
 HOMEPAGE="https://www.chromium.org/chromium-os/chromiumos-design-docs/chromium-os-kernel"
 KEYWORDS="*"
 IUSE="module_sign gpu"
@@ -160,3 +155,14 @@
 	# Install kernel commit information
 	write_kernel_commit
 }
+
+# Change the following (commented out) number to the next prime number
+# when you change base.config.  This workaround will force the
+# ChromeOS CQ to uprev sys-kernel/lakitu-kernel-4_19 ebuild and pick up the
+# configuration changes.  In absence of this workaround the config changes
+# would not be picked up unless there was a code change in kernel source tree.
+#
+# NOTE: There's nothing magic keeping this number prime but you just need to
+# make _any_ change to this file.  ...so why not keep it prime?
+#
+# The coolest prime number is: 47