Move current requirements to v/ folder.

Like compatibility matrices, we no longer maintains
a current version of the kernel requirements. All
kernel requirements are denoted with the dessert
release.

Test: TH
Change-Id: Ic0bc57c4e78d2f038d70bf0286a89625687947ef

README.md

@@ -157,23 +157,6 @@ Build rules from the aforementioned files to a
 [this link](https://source.android.com/devices/architecture/vintf/match-rules#kernel)
 for details of the output format.
 
-## I want to freeze/release the current kernel requirements. What do I do?
-
-Prior to a [FCM Version release](https://source.android.com/devices/architecture/vintf/fcm#new-fcm-versions)
-(often accompanied with a dessert release as well), the kernel requirements must
-be frozen. Follow the following steps
-
-* Copy the top-level `android-*` directories to a release directory, preferably
-  with the dessert name (for example, `q`).
-  * Remove top-level `android-*` directories. This change is not propagated to
-    master.
-* Edit the new `<dessert>/android-*/Android.bp` files and rename the modules.
-  For example, change `kernel_config_current_4.9` in `q/android-4.9/Android.bp`
-  to `kernel_config_q_4.9`
-* Under `hardware/interfaces/compatibility_matrices/Android.bp`, edit
-  `kernel_configs` field for the `framework_compatibility_matrix.<level>.xml`
-  to use the new modules.
-
 ## I want to edit a released kernel requirement. What do I do?
 
 Don't edit a released kernel requirement unless necessary. If you have to make

v/android-5.15/Android.bp

@@ -18,7 +18,7 @@ package {
 }
 
 kernel_config {
-    name: "kernel_config_current_5.15",
+    name: "kernel_config_v_5.15",
     srcs: [
         "android-base.config",
     ],

v/android-6.1/Android.bp

@@ -18,7 +18,7 @@ package {
 }
 
 kernel_config {
-    name: "kernel_config_current_6.1",
+    name: "kernel_config_v_6.1",
     srcs: [
         "android-base.config",
     ],