NothingOSS/android_kernel_msm-6.1_nothing_sm7635
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Kernel Source and devicetree for NOTHING Phone(3a) and Phone(3a)Pro
1146278 commits 1 branch 0 tags 2.6 GiB
Find a file
Todd Kjos bbabedc499 ANDROID: GKI: 3/1/2023 KMI update 
Set KMI_GENERATION=1 for 3/1 KMI update

Location: "abi_stgdiff/abi.report.short"
Analyzer Description: Compare committed and generated ABI representations.
Owner: libabigail@google.com

ABI is broken for 'kernel_abi_aarch64' on 'aosp_kernel-common-android14-6.1'!, please visit go/kernel-abi-monitoring

function symbol 'void __ClearPageMovable(struct page*)' changed
  CRC changed from 0x754c1034 to 0x6f60ec1b

function symbol 'void __SetPageMovable(struct page*, const struct movable_operations*)' changed
  CRC changed from 0x662946a3 to 0xd0d79e98

function symbol 'int ___pskb_trim(struct sk_buff*, unsigned int)' changed
  CRC changed from 0x7320a9c0 to 0x28c5c2a1

... 3536 omitted; 3539 symbols have only CRC changes

type 'struct module' changed
  byte size changed from 960 to 1024
  member 'const char* scmversion' was added
  16 members ('struct kobject* holders_dir' .. 'int(* init)()') changed
    offset changed by 64
  42 members ('struct module_layout core_layout' .. 'atomic_t refcnt') changed
    offset changed by 512

type 'struct crypto_aead' changed
  byte size changed from 256 to 128
  member 'struct crypto_tfm base' changed
    offset changed by -512

type 'struct crypto_ahash' changed
  byte size changed from 256 to 192

type 'struct crypto_tfm' changed
  byte size changed from 128 to 64
  member 'void* __crt_ctx[0]' changed
    offset changed by -512

type 'struct crypto_kpp' changed
  byte size changed from 128 to 64

type 'struct crypto_shash' changed
  byte size changed from 256 to 128
  member 'struct crypto_tfm base' changed
    offset changed by -512

type 'struct crypto_skcipher' changed
  byte size changed from 256 to 128
  member 'struct crypto_tfm base' changed
    offset changed by -512

type 'struct crypto_sync_skcipher' changed
  byte size changed from 256 to 128

type 'struct crypto_comp' changed
  byte size changed from 128 to 64

type 'struct crypto_rng' changed
  byte size changed from 128 to 64

type 'struct aead_alg' changed
  byte size changed from 512 to 448
  member 'struct crypto_alg base' changed
    offset changed by -512

type 'struct ahash_alg' changed
  byte size changed from 640 to 576

type 'struct rng_alg' changed
  byte size changed from 512 to 448
  member 'struct crypto_alg base' changed
    offset changed by -512

type 'struct shash_alg' changed
  byte size changed from 640 to 576
  member 'struct crypto_alg base' changed
    offset changed by -512

type 'struct skcipher_alg' changed
  byte size changed from 512 to 448
  member 'struct crypto_alg base' changed
    offset changed by -512

type 'struct hash_alg_common' changed
  byte size changed from 512 to 448
  member 'struct crypto_alg base' changed
    offset changed by -512

type 'struct crypto_instance' changed
  byte size changed from 512 to 448
  member 'void* __ctx[0]' changed
    offset changed by -512

Bug: 271188187
Change-Id: I985ca51c3c057e10ad8437956389b31561ddfbf9
Signed-off-by: Todd Kjos <tkjos@google.com>
2023-03-01 16:22:29 +00:00
android ANDROID: GKI: 3/1/2023 KMI update 2023-03-01 16:22:29 +00:00
arch ANDROID: GKI: Enable CONFIG_MODULE_SCMVERSION=y 2023-03-01 01:47:13 +00:00
block FROMGIT: blk-mq: move the call to blk_put_queue out of blk_mq_destroy_queue 2023-02-23 17:09:21 +00:00
certs This is the 6.1.11 stable release 2023-02-09 13:29:55 +00:00
crypto This is the 6.1.11 stable release 2023-02-09 13:29:55 +00:00
Documentation ANDROID: modules: re-introduce the MODULE_SCMVERSION config 2023-03-01 01:47:13 +00:00
drivers Merge "Merge 6.1.14 into android14-6.1" into android14-6.1 2023-02-28 12:00:57 +00:00
fs This is the 6.1.14 stable release 2023-02-25 15:37:47 +00:00
include Revert "ANDROID: GKI: skip btf_type_tag in genksyms" 2023-03-01 01:47:13 +00:00
init This is the 6.1.6 stable release 2023-01-18 18:50:42 +00:00
io_uring use less confusing names for iov_iter direction initializers 2023-02-09 11:28:04 +01:00
ipc ipc: fix memory leak in init_mqueue_fs() 2022-12-31 13:32:01 +01:00
kernel ANDROID: modules: re-introduce the MODULE_SCMVERSION config 2023-03-01 01:47:13 +00:00
lib This is the 6.1.14 stable release 2023-02-25 15:37:47 +00:00
LICENSES LICENSES/LGPL-2.1: Add LGPL-2.1-or-later as valid identifiers 2021-12-16 14:33:10 +01:00
mm ANDROID: mm: add reclaim_shmem_address_space() for faster reclaims 2023-02-23 22:51:35 +00:00
net This is the 6.1.13 stable release 2023-02-22 12:32:41 +00:00
rust rust: print: avoid evaluating arguments in pr_* macros in unsafe blocks 2023-02-06 08:06:34 +01:00
samples This is the 6.1.9 stable release 2023-02-01 09:12:59 +00:00
scripts ANDROID: modules: re-introduce the MODULE_SCMVERSION config 2023-03-01 01:47:13 +00:00
security This is the 6.1.14 stable release 2023-02-25 15:37:47 +00:00
sound This is the 6.1.13 stable release 2023-02-22 12:32:41 +00:00
tools This is the 6.1.14 stable release 2023-02-25 15:37:47 +00:00
usr usr/gen_init_cpio.c: remove unnecessary -1 values from int file 2022-10-03 14:21:44 -07:00
virt kvm/vfio: Fix potential deadlock on vfio group_lock 2023-02-01 08:34:36 +01:00
.clang-format inet: ping: use hlist_nulls rcu iterator during lookup 2022-12-01 12:42:46 +01:00
.cocciconfig
.get_maintainer.ignore get_maintainer: add Alan to .get_maintainer.ignore 2022-08-20 15:17:44 -07:00
.gitattributes
.gitignore Kbuild: add Rust support 2022-09-28 09:02:20 +02:00
.mailmap 9 hotfixes. 6 for MM, 3 for other areas. Four of these patches address 2022-12-10 17:10:52 -08:00
.rustfmt.toml rust: add .rustfmt.toml 2022-09-28 09:02:20 +02:00
BUILD.bazel ANDROID: Add initial symbols list for db845c 2023-02-27 11:32:18 +00:00
build.config.aarch64 ANDROID: Move NDK_TRIPLE to build.config.constants. 2023-02-14 14:13:51 -08:00
build.config.allmodconfig ANDROID: allmodconfig: Disable RANDSTRUCT 2022-12-01 10:37:28 +00:00
build.config.allmodconfig.aarch64
build.config.allmodconfig.arm
build.config.allmodconfig.x86_64
build.config.amlogic
build.config.arm ANDROID: build.config: set NDK_TRIPLE 2022-04-05 14:09:03 -07:00
build.config.common ANDROID: GKI: 3/1/2023 KMI update 2023-03-01 16:22:29 +00:00
build.config.constants ANDROID: Move NDK_TRIPLE to build.config.constants. 2023-02-14 14:13:51 -08:00
build.config.db845c ANDROID: Convert db845c to a mixed build. 2022-09-06 23:21:51 +00:00
build.config.gki ANDROID: GKI: Source GKI_BUILD_CONFIG_FRAGMENT after setting all variables 2022-12-27 13:52:08 -08:00
build.config.gki-debug.aarch64
build.config.gki-debug.x86_64
build.config.gki.aarch64 ANDROID: GKI: Source GKI_BUILD_CONFIG_FRAGMENT after setting all variables 2022-12-27 13:52:08 -08:00
build.config.gki.aarch64.16k ANDROID: 16k target: don't write defconfig to source tree 2022-10-03 11:24:35 -07:00
build.config.gki.aarch64.fips140 ANDROID: fips140: add kernel crypto module 2023-01-09 21:33:43 +00:00
build.config.gki.riscv64 ANDROID: GKI: Source GKI_BUILD_CONFIG_FRAGMENT after setting all variables 2022-12-27 13:52:08 -08:00
build.config.gki.x86_64 ANDROID: GKI: Source GKI_BUILD_CONFIG_FRAGMENT after setting all variables 2022-12-27 13:52:08 -08:00
build.config.gki_kasan ANDROID: build.config: re-disable LTO properly for KASAN 2022-03-24 12:41:35 -07:00
build.config.gki_kasan.aarch64
build.config.gki_kasan.x86_64
build.config.gki_kprobes
build.config.gki_kprobes.aarch64
build.config.gki_kprobes.x86_64
build.config.khwasan ANDROID: Add a build config fragment for KHWASan. 2021-10-13 19:44:44 +00:00
build.config.riscv64 ANDROID: GKI: Add 64-bit RISC-V config 2022-12-08 20:01:15 +00:00
build.config.rockpi4 ANDROID: rockpi4: Use new DTS_EXT_DIR feature 2021-12-13 21:27:46 +00:00
build.config.x86_64 ANDROID: Move NDK_TRIPLE to build.config.constants. 2023-02-14 14:13:51 -08:00
COPYING
CREDITS MAINTAINERS: Remove Michal Marek from Kbuild maintainers 2022-11-16 14:53:00 +09:00
Kbuild Kbuild updates for v6.1 2022-10-10 12:00:45 -07:00
Kconfig ANDROID: kbuild: add Kconfig support for external modules 2021-12-13 18:33:18 +00:00
Kconfig.ext ANDROID: kbuild: add Kconfig support for external modules 2021-12-13 18:33:18 +00:00
MAINTAINERS This is the 6.1.14 stable release 2023-02-25 15:37:47 +00:00
Makefile This is the 6.1.14 stable release 2023-02-25 15:37:47 +00:00
modules.bzl ANDROID: GKI: Fix linter warning 2022-12-01 13:06:20 +00:00
OWNERS ANDROID: add smuckle to OWNERS 2022-06-18 10:41:40 -07:00
OWNERS_DrNo ANDROID: Updating OWNERS_DrNo 2022-08-22 16:34:52 +00:00
README
README.md

README.md

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. These patches will be merged automatically in the corresponding common kernels. If the patch is already in upstream Linux, post a backport of the patch that conforms to the patch requirements below.

    • Do not send patches upstream that contain only symbol exports. To be considered for upstream Linux, additions of EXPORT_SYMBOL_GPL() require an in-tree modular driver that uses the symbol -- so include the new driver or changes to an existing driver in the same patchset as the export.
    • When sending patches upstream, the commit message must contain a clear case for why the patch is needed and beneficial to the community. Enabling out-of-tree drivers or functionality is not not a persuasive case.

  2. LESS GOOD: Develop your patches out-of-tree (from an upstream Linux point-of-view). Unless these are fixing an Android-specific bug, these are very unlikely to be accepted unless they have been coordinated with kernel-team@android.com. If you want to proceed, post a patch that conforms to the patch requirements below.

Common Kernel patch requirements

  • All patches must conform to the Linux kernel coding standards and pass scripts/checkpatch.pl
  • 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:.
  • 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

Additional requirements are listed below based on patch type

Requirements for backports from mainline Linux: UPSTREAM:, BACKPORT:

  • If the patch is a cherry-pick from Linux mainline with no changes at all
    • tag the patch subject with UPSTREAM:.
    • add upstream commit information with a (cherry picked from commit ...) line
    • Example:
      • if the upstream commit message is
        important patch from upstream

        This is the detailed description of the important patch

        Signed-off-by: Fred Jones <fred.jones@foo.org>
  • then Joe Smith would upload the patch for the common kernel as
        UPSTREAM: important patch from upstream

        This is the detailed description of the important patch

        Signed-off-by: Fred Jones <fred.jones@foo.org>

        Bug: 135791357
        Change-Id: I4caaaa566ea080fa148c5e768bb1a0b6f7201c01
        (cherry picked from commit c31e73121f4c1ec41143423ac6ce3ce6dafdcec1)
        Signed-off-by: Joe Smith <joe.smith@foo.org>
  • If the patch requires any changes from the upstream version, tag the patch with BACKPORT: instead of UPSTREAM:.
    • use the same tags as UPSTREAM:
    • add comments about the changes under the (cherry picked from commit ...) line
    • Example:
        BACKPORT: important patch from upstream

        This is the detailed description of the important patch

        Signed-off-by: Fred Jones <fred.jones@foo.org>

        Bug: 135791357
        Change-Id: I4caaaa566ea080fa148c5e768bb1a0b6f7201c01
        (cherry picked from commit c31e73121f4c1ec41143423ac6ce3ce6dafdcec1)
        [joe: Resolved minor conflict in drivers/foo/bar.c ]
        Signed-off-by: Joe Smith <joe.smith@foo.org>

Requirements for other backports: FROMGIT:, FROMLIST:,

  • If the patch has been merged into an upstream maintainer tree, but has not yet been merged into Linux mainline
    • tag the patch subject with FROMGIT:
    • add info on where the patch came from as (cherry picked from commit <sha1> <repo> <branch>). This must be a stable maintainer branch (not rebased, so don't use linux-next for example).
    • if changes were required, use BACKPORT: FROMGIT:
    • Example:
      • if the commit message in the maintainer tree is
        important patch from upstream

        This is the detailed description of the important patch

        Signed-off-by: Fred Jones <fred.jones@foo.org>
  • then Joe Smith would upload the patch for the common kernel as
        FROMGIT: important patch from upstream

        This is the detailed description of the important patch

        Signed-off-by: Fred Jones <fred.jones@foo.org>

        Bug: 135791357
        (cherry picked from commit 878a2fd9de10b03d11d2f622250285c7e63deace
         https://git.kernel.org/pub/scm/linux/kernel/git/foo/bar.git test-branch)
        Change-Id: I4caaaa566ea080fa148c5e768bb1a0b6f7201c01
        Signed-off-by: Joe Smith <joe.smith@foo.org>
  • 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
    • add a Bug: tag with the Android bug (required for patches not accepted into a maintainer tree)
    • if changes were required, use BACKPORT: FROMLIST:
    • Example:
        FROMLIST: important patch from upstream

        This is the detailed description of the important patch

        Signed-off-by: Fred Jones <fred.jones@foo.org>

        Bug: 135791357
        Link: https://lore.kernel.org/lkml/20190619171517.GA17557@someone.com/
        Change-Id: I4caaaa566ea080fa148c5e768bb1a0b6f7201c01
        Signed-off-by: Joe Smith <joe.smith@foo.org>

Requirements for Android-specific patches: ANDROID:

  • If the patch is fixing a bug to Android-specific code
    • tag the patch subject with ANDROID:
    • add a Fixes: tag that cites the patch with the bug
    • Example:
        ANDROID: fix android-specific bug in foobar.c

        This is the detailed description of the important fix

        Fixes: 1234abcd2468 ("foobar: add cool feature")
        Change-Id: I4caaaa566ea080fa148c5e768bb1a0b6f7201c01
        Signed-off-by: Joe Smith <joe.smith@foo.org>
  • 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)