A-Team_Digital_Solutions/android_kernel_motorola_sm6375
Watch
2
0
Fork
You've already forked android_kernel_motorola_sm6375
 0
mirror of https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git synced 2026-10-07 12:25:00 -04:00
Code Issues Projects Releases Packages Wiki Activity
No description
879,449 commits 10 branches 0 tags 2.1 GiB
  • C 98.2%
  • Assembly 1%
  • Makefile 0.3%
  • Shell 0.2%
  • Python 0.1%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Satya Tangirala 2c6b2164e6 ANDROID: gki_defconfig: enable CONFIG_MMC_CRYPTO 
Enable inline encryption support in MMC core.

Leaf changes summary: 5 artifacts changed
Changed leaf types summary: 5 leaf types changed
Removed/Changed/Added functions summary: 0 Removed, 0 Changed, 0 Added function
Removed/Changed/Added variables summary: 0 Removed, 0 Changed, 0 Added variable

'struct hc_driver at hcd.h:255:1' changed:
  type size changed from 3136 to 3264 (in bits)
  1 data member insertion:
    'unsigned long int hc_driver::android_vendor_data[2]', at offset 2880 (in bits) at hcd.h:419:1
  there are data member changes:
    'u64 hc_driver::android_kabi_reserved1' offset changed from 2880 to 3008 (in bits) (by +128 bits)
    'u64 hc_driver::android_kabi_reserved2' offset changed from 2944 to 3072 (in bits) (by +128 bits)
    'u64 hc_driver::android_kabi_reserved3' offset changed from 3008 to 3136 (in bits) (by +128 bits)
    'u64 hc_driver::android_kabi_reserved4' offset changed from 3072 to 3200 (in bits) (by +128 bits)
  16 impacted interfaces

'struct mmc_host at host.h:271:1' changed:
  type size changed from 12288 to 13312 (in bits)
  2 data member insertions:
    'keyslot_manager* mmc_host::ksm', at offset 12288 (in bits) at host.h:467:1
    'void* mmc_host::crypto_DO_NOT_USE[7]', at offset 12352 (in bits) at host.h:468:1
  there are data member changes:
    'bool mmc_host::hsq_enabled' offset changed from 12272 to 12800 (in bits) (by +528 bits)
    'unsigned long int mmc_host::private[]' offset changed from 12288 to 13312 (in bits) (by +1024 bits)
  87 impacted interfaces

'struct mmc_request at core.h:147:1' changed:
  type size changed from 1024 to 1216 (in bits)
  3 data member insertions:
    'int mmc_request::crypto_key_slot', at offset 1024 (in bits) at core.h:169:1
    'u64 mmc_request::data_unit_num', at offset 1088 (in bits) at core.h:170:1
    'const blk_crypto_key* mmc_request::crypto_key', at offset 1152 (in bits) at core.h:171:1
  87 impacted interfaces

'struct ufs_hba at ufshcd.h:589:1' changed:
  type size changed from 29440 to 29952 (in bits)
  1 data member insertion:
    'void* ufs_hba::crypto_DO_NOT_USE[8]', at offset 29184 (in bits) at ufshcd.h:826:1
  there are data member changes:
    'u64 ufs_hba::android_kabi_reserved1' offset changed from 29184 to 29696 (in bits) (by +512 bits)
    'u64 ufs_hba::android_kabi_reserved2' offset changed from 29248 to 29760 (in bits) (by +512 bits)
    'u64 ufs_hba::android_kabi_reserved3' offset changed from 29312 to 29824 (in bits) (by +512 bits)
    'u64 ufs_hba::android_kabi_reserved4' offset changed from 29376 to 29888 (in bits) (by +512 bits)
  13 impacted interfaces

'struct ufs_hba_crypto_variant_ops at ufshcd.h:371:1' changed:
  type size changed from 1024 to 1536 (in bits)
  1 data member insertion:
    'void* ufs_hba_crypto_variant_ops::crypto_DO_NOT_USE[8]', at offset 768 (in bits) at ufshcd.h:391:1
  there are data member changes:
    'u64 ufs_hba_crypto_variant_ops::android_kabi_reserved1' offset changed from 768 to 1280 (in bits) (by +512 bits)
    'u64 ufs_hba_crypto_variant_ops::android_kabi_reserved2' offset changed from 832 to 1344 (in bits) (by +512 bits)
    'u64 ufs_hba_crypto_variant_ops::android_kabi_reserved3' offset changed from 896 to 1408 (in bits) (by +512 bits)
    'u64 ufs_hba_crypto_variant_ops::android_kabi_reserved4' offset changed from 960 to 1472 (in bits) (by +512 bits)
  13 impacted interfaces

Bug: 153512828
Bug: 144046242
Change-Id: I1bdf922c2373c0d756864df2c329d7a8179fe09e
Signed-off-by: Satya Tangirala <satyat@google.com>
2020-04-23 21:17:05 +00:00
arch ANDROID: gki_defconfig: enable CONFIG_MMC_CRYPTO 2020-04-23 21:17:05 +00:00
block This is the 5.4.35 stable release 2020-04-23 11:15:10 +02:00
certs
crypto This is the 5.4.33 stable release 2020-04-17 11:26:58 +02:00
Documentation This is the 5.4.35 stable release 2020-04-23 11:15:10 +02:00
drivers ANDROID: Add padding for crypto related structs in UFS and MMC 2020-04-23 20:48:15 +00:00
fs ANDROID: sdcardfs: fix export symbol types 2020-04-23 14:21:31 +02:00
include ANDROID: Add padding for crypto related structs in UFS and MMC 2020-04-23 20:48:15 +00:00
init ANDROID: init: GKI: enable hidden configs for GPU 2020-04-22 20:40:03 +00:00
ipc This is the 5.4.23 stable release 2020-03-01 10:17:44 +01:00
kernel This is the 5.4.35 stable release 2020-04-23 11:15:10 +02:00
lib This is the 5.4.35 stable release 2020-04-23 11:15:10 +02:00
LICENSES
mm This is the 5.4.33 stable release 2020-04-17 11:26:58 +02:00
net This is the 5.4.35 stable release 2020-04-23 11:15:10 +02:00
samples FROMGIT: samples/hw_breakpoint: drop use of kallsyms_lookup_name() 2020-03-12 11:15:54 +00:00
scripts FROMGIT: kbuild: mkcompile_h: Include $LD version in /proc/version 2020-04-08 16:27:24 +00:00
security This is the 5.4.35 stable release 2020-04-23 11:15:10 +02:00
sound This is the 5.4.35 stable release 2020-04-23 11:15:10 +02:00
tools This is the 5.4.35 stable release 2020-04-23 11:15:10 +02:00
usr initramfs: restore default compression behavior 2020-04-08 09:08:38 +02:00
virt KVM: Check for a bad hva before dropping into the ghc slow path 2020-03-05 16:43:48 +01:00
.clang-format clang-format: Update with the latest for_each macro list 2019-08-31 10:00:51 +02:00
.cocciconfig
.get_maintainer.ignore
.gitattributes
.gitignore Revert "ANDROID: Revert "Merge tag 'modules-for-v5.4' of git://git.kernel.org/pub/scm/linux/kernel/git/jeyu/linux"" 2019-11-13 10:14:45 +00:00
.mailmap ARM: SoC fixes 2019-11-10 13:41:59 -08:00
abi_gki_aarch64.xml ANDROID: gki_defconfig: enable CONFIG_MMC_CRYPTO 2020-04-23 21:17:05 +00:00
abi_gki_aarch64_cuttlefish_whitelist ANDROID: GKI: update cf whitelist + gki whitelist 2020-03-31 12:28:54 -07:00
abi_gki_aarch64_db845c_whitelist ANDROID: ABI/Whitelist: update for db845c after changing drivers to modules. 2020-04-16 18:15:41 +00:00
abi_gki_aarch64_goldfish_whitelist ANDROID: GKI: Added goldfish whitelist to aarch64 abi 2020-03-31 12:45:07 -07:00
abi_gki_aarch64_hikey960_whitelist ANDROID: ABI/Whitelist: update for hikey960 2020-03-23 23:39:45 +00:00
abi_gki_aarch64_qcom_whitelist ANDROID: GKI: remove kernel_read/write from whitelists 2020-04-02 06:18:20 +00:00
abi_gki_aarch64_unisoc_whitelist ANDROID: ABI/Whitelist: update unisoc Whitelist to latest 2020-04-23 13:23:58 +08:00
abi_gki_aarch64_whitelist ANDROID: abi_gki_aarch64_whitelist: add module_layout and task_struct 2020-03-04 23:09:20 +00:00
build.config.aarch64 ANDROID: support GKI image that contains an uncompressed Kernel Image. 2020-02-06 11:14:03 +00:00
build.config.allmodconfig ANDROID: fix allmodconfig build to use the right toolchain 2020-04-14 15:39:56 +00:00
build.config.allmodconfig.aarch64 ANDROID: create build.configs for allmodconfig 2019-09-04 15:49:40 +00:00
build.config.allmodconfig.arm ANDROID: Add build.config files for ARM 32-bit 2020-03-15 22:51:11 +00:00
build.config.allmodconfig.x86_64 ANDROID: create build.configs for allmodconfig 2019-09-04 15:49:40 +00:00
build.config.arm ANDROID: Add build.config files for ARM 32-bit 2020-03-15 22:51:11 +00:00
build.config.common ANDROID: clang: update to 10.0.5 2020-03-30 20:09:25 +00:00
build.config.db845c ANDROID: db845c build: Use merge_configs 2020-04-01 14:04:53 +00:00
build.config.gki ANDROID: gki: Removed cf modules from gki_defconfig 2020-01-31 16:34:58 -08:00
build.config.gki-debug.aarch64 ANDROID: Add build.config.gki-debug.aarch64 2020-03-16 09:20:25 +00:00
build.config.gki-debug.x86_64 ANDROID: Add build.config.gki-debug.x86_64 2020-03-16 14:27:00 +00:00
build.config.gki.aarch64 ANDROID: GKI: Added goldfish whitelist to aarch64 abi 2020-03-31 12:45:07 -07:00
build.config.gki.x86_64 ANDROID: refactor build.config files to remove duplication 2019-08-30 14:55:29 +01:00
build.config.hikey960 ANDROID: hikey960: Add external mali driver support to build.config.hikey960 2020-03-23 22:55:17 +00:00
build.config.x86_64 ANDROID: refactor build.config files to remove duplication 2019-08-30 14:55:29 +01:00
COPYING
CREDITS MAINTAINERS: Remove Simon as Renesas SoC Co-Maintainer 2019-10-10 08:12:51 -07:00
Kbuild
Kconfig
MAINTAINERS This is the 5.4.23 stable release 2020-03-01 10:17:44 +01:00
Makefile This is the 5.4.35 stable release 2020-04-23 11:15:10 +02:00
README
README.md ANDROID: Fix typo for FROMLIST: section 2019-10-29 20:31:07 +00:00

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.

  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 script/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 ...) 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 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 ...) 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 c31e73121f4c1ec41143423ac6ce3ce6dafdcec1)
        [ 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
    • 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)