From 53bdce6ba932fbb31e9fc9f4d21dea0d7c93b2f4 Mon Sep 17 00:00:00 2001 From: mmollaharif803 <60807815+mmollaharif803@users.noreply.github.com> Date: Thu, 30 Apr 2026 17:32:57 +0300 Subject: [PATCH] Update README with Xiaomi Redmi 15 5G kernel info Added stock kernel release information for Xiaomi Redmi 15 5G. --- README.md | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 4a1deb36d391d..43aaeeb269e5b 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,15 @@ +# Squid Kernel — Xiaomi Redmi 15 5G (spring) + +Stock kernel release by [suchit-7x](https://github.com/suchit-7x): + +[ + +![Download Stock Release](https://img.shields.io/badge/Download-Stock%20Release-blue) + +](https://github.com/suchit-7x/kernel_xiaomi_spring/releases/tag/stock) + +--- + # How do I submit patches to Android Common Kernels 1. BEST: Make all of your changes to upstream Linux. If appropriate, backport to the stable releases. @@ -21,7 +33,7 @@ not a persuasive case. - Patches shall not break gki_defconfig or allmodconfig builds for arm, arm64, x86, x86_64 architectures (see https://source.android.com/setup/build/building-kernels) - If the patch is not merged from an upstream branch, the subject must be tagged with the type of patch: -`UPSTREAM:`, `BACKPORT:`, `FROMGIT:`, `FROMLIST:`, or `ANDROID:`. + `UPSTREAM:`, `BACKPORT:`, `FROMGIT:`, `FROMLIST:`, or `ANDROID:`. - All patches must have a `Change-Id:` tag (see https://gerrit-review.googlesource.com/Documentation/user-changeid.html) - If an Android bug has been assigned, there must be a `Bug:` tag. - All patches must have a `Signed-off-by:` tag by the author and the submitter @@ -107,7 +119,6 @@ must be a stable maintainer branch (not rebased, so don't use `linux-next` for e Signed-off-by: Joe Smith ``` - - If the patch has been submitted to LKML, but not accepted into any maintainer tree - tag the patch subject with `FROMLIST:` - add a `Link:` tag with a link to the submittal on lore.kernel.org @@ -147,4 +158,3 @@ a maintainer tree) - If the patch is a new feature - tag the patch subject with `ANDROID:` - add a `Bug:` tag with the Android bug (required for android-specific features) -