ANDROID: GKI: update .xml file

No one has done it in a while:

Leaf changes summary: 1776 artifacts changed
Changed leaf types summary: 2 leaf types changed
Removed/Changed/Added functions summary: 0 Removed, 1741 Changed, 12 Added functions
Removed/Changed/Added variables summary: 0 Removed, 20 Changed, 1 Added variable

12 Added functions:

  [A] 'function unsigned long int ZSTD_CCtxWorkspaceBound(__anonymous_struct__1)'
  [A] 'function unsigned long int ZSTD_DCtxWorkspaceBound()'
  [A] 'function unsigned long int ZSTD_compressCCtx(ZSTD_CCtx_s*, void*, unsigned long int, void*, unsigned long int, __anonymous_struct__)'
  [A] 'function unsigned long int ZSTD_decompressDCtx(ZSTD_DCtx_s*, void*, unsigned long int, void*, unsigned long int)'
  [A] 'function __anonymous_struct__ ZSTD_getParams(int, long long unsigned int, unsigned long int)'
  [A] 'function ZSTD_CCtx_s* ZSTD_initCCtx(void*, unsigned long int)'
  [A] 'function ZSTD_DCtx_s* ZSTD_initDCtx(void*, unsigned long int)'
  [A] 'function dma_heap* dma_heap_add(const dma_heap_export_info*)'
  [A] 'function device* dma_heap_get_dev(dma_heap*)'
  [A] 'function void* dma_heap_get_drvdata(dma_heap*)'
  [A] 'function void usb_hcd_end_port_resume(usb_bus*, int)'
  [A] 'function void usb_hcd_start_port_resume(usb_bus*, int)'

1741 functions with some sub-type change:
'struct iommu_ops at iommu.h:250:1' changed:
  type size hasn't changed
  there are data member changes:
    type 'int (iommu_domain*, unsigned long int, typedef phys_addr_t, typedef size_t, int)*' of 'iommu_ops::map' changed:
      pointer type changed from: 'int (iommu_domain*, unsigned long int, typedef phys_addr_t, typedef size_t, int)*' to: 'int (iommu_domain*, unsigned long int, typedef phys_addr_t, typedef size_t, int, typedef gfp_t)*'
  2916 impacted interfaces

'struct signal_struct at signal.h:81:1' changed:
  type size changed from 8576 to 8704 (in bits)
  there are data member changes:
    type 'struct mutex' of 'signal_struct::exec_update_mutex' changed:
      type name changed from 'mutex' to 'rw_semaphore'
      type size changed from 256 to 384 (in bits)
      2 data member insertions:
        'atomic_long_t rw_semaphore::count', at offset 0 (in bits) at rwsem.h:37:1
        'u64 rw_semaphore::android_vendor_data1', at offset 320 (in bits) at rwsem.h:55:1
      there are data member changes:
        'atomic_long_t mutex::owner' offset changed from 0 to 64 (in bits) (by +64 bits)
        type 'typedef spinlock_t' of 'mutex::wait_lock' changed:
          typedef name changed from spinlock_t to raw_spinlock_t at spinlock_types.h:29:1
          underlying type 'struct spinlock' at spinlock_types.h:61:1 changed:
            type name changed from 'spinlock' to 'raw_spinlock'
            type size hasn't changed
            there are data member changes:
              anonymous data member union {raw_spinlock rlock;} at offset 0 (in bits) became data member 'arch_spinlock_t raw_spinlock::raw_lock'
        and name of 'mutex::wait_lock' changed to 'rw_semaphore::wait_lock' at rwsem.h:47:1, offset changed from 64 to 160 (in bits) (by +96 bits)
        'optimistic_spin_queue mutex::osq' offset changed from 96 to 128 (in bits) (by +32 bits)
        'list_head mutex::wait_list' offset changed from 128 to 192 (in bits) (by +64 bits)
    and name of 'signal_struct::exec_update_mutex' changed to 'signal_struct::exec_update_lock' at signal.h:232:1
    'u64 signal_struct::android_kabi_reserved1' offset changed from 8320 to 8448 (in bits) (by +128 bits)
    'u64 signal_struct::android_kabi_reserved2' offset changed from 8384 to 8512 (in bits) (by +128 bits)
    'u64 signal_struct::android_kabi_reserved3' offset changed from 8448 to 8576 (in bits) (by +128 bits)
    'u64 signal_struct::android_kabi_reserved4' offset changed from 8512 to 8640 (in bits) (by +128 bits)
  2916 impacted interfaces

Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Change-Id: I95846c7341d73a1097b779cc55698dab66d1e5f3
1 file changed
tree: 4f21b1ced05d9e5d33d363cffdb18d8f663495f5
  1. android/
  2. arch/
  3. block/
  4. certs/
  5. crypto/
  6. Documentation/
  7. drivers/
  8. fs/
  9. include/
  10. init/
  11. ipc/
  12. kernel/
  13. lib/
  14. LICENSES/
  15. mm/
  16. net/
  17. samples/
  18. scripts/
  19. security/
  20. sound/
  21. tools/
  22. usr/
  23. virt/
  24. .clang-format
  25. .cocciconfig
  26. .get_maintainer.ignore
  27. .gitattributes
  28. .gitignore
  29. .mailmap
  30. build.config.aarch64
  31. build.config.allmodconfig
  32. build.config.allmodconfig.aarch64
  33. build.config.allmodconfig.arm
  34. build.config.allmodconfig.x86_64
  35. build.config.arm
  36. build.config.common
  37. build.config.db845c
  38. build.config.gki
  39. build.config.gki-debug.aarch64
  40. build.config.gki-debug.x86_64
  41. build.config.gki.aarch64
  42. build.config.gki.x86_64
  43. build.config.gki_kasan
  44. build.config.gki_kasan.aarch64
  45. build.config.gki_kasan.x86_64
  46. build.config.hikey960
  47. build.config.x86_64
  48. COPYING
  49. CREDITS
  50. Kbuild
  51. Kconfig
  52. MAINTAINERS
  53. Makefile
  54. README
  55. 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.

  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)