16 Dec, 2020

1 commit


14 Dec, 2020

1 commit


10 Nov, 2020

1 commit

  • Enable the use of the hermetic toolchain across all builds of this
    branch. For allmodconfig builds, also allow the use of openssl from the
    host.

    Bug: 157507870
    Change-Id: Iabb1fe4f760f9821df0318934942302ffffade7c
    Signed-off-by: Matthias Maennich

    Matthias Maennich
     

28 Oct, 2020

1 commit


23 Sep, 2020

1 commit

  • This moves builds to all use LLVM=1 argument to make, rather than
    CC=clang NM=llvm-nm OBJCOPY=llvm-objcopy ... (see also
    https://www.kernel.org/doc/html/latest/kbuild/llvm.html#llvm-utilities).

    Step 3 of aosp/1405387.

    Bug: 65987925
    Bug: 141693040
    Signed-off-by: Nick Desaulniers
    Change-Id: I0975dcad48b6c5344124343606e1c7f85e76e4ee

    Nick Desaulniers
     

31 Aug, 2020

1 commit

  • And replace many references of ${ROOT_DIR}/common with
    ${ROOT_DIR}/${KERNEL_DIR}, which makes it a lot easier
    to branch off of ACK and update the KERNEL_DIR.

    The variable of KERNEL_DIR will be set in build/_setup_env.sh
    to the directory of the build config file by default if it's
    not set explicitly in the build config file or in environment.

    Test: build test with following configs
    common/build.config.gki.aarch64
    common/build.config.db845c
    common/build.config.hikey960
    cuttlefish-modules/build.config.cuttlefish.aarch64

    Bug: 162785964
    Change-Id: I790ac0ded10bd790484f14c6f93d53e06c38b830
    Signed-off-by: Will McVicker
    Signed-off-by: Yongqin Liu
    (cherry picked from commit 931718fa65fe5e34d143250c048f591a7d74e5f8)
    [elavila: resolve conflicts]
    Signed-off-by: J. Avila

    Will McVicker
     

19 Aug, 2020

1 commit


28 Jul, 2020

1 commit

  • The new kernel release format is: w.x.y-zz-k where,
    w.x.y are the current values
    zzz is the Android Release value
    k is the KMI Generation number

    This allows one to identify the kernel module interface version using
    `uname -r`. The KMI Generation number is used to identify any KMI
    changes that occur after the KMI freeze. This should only occur in an
    unlikely event that a security patch requires a KMI update.

    Here is a local example:
    5.4.51-android12-0-00153-ga972f59040e4-dirty

    Signed-off-by: Will McVicker
    Bug: 159842160
    Change-Id: I33f40e424ca967b85d810cdb12c6a2c58e4197b7
    [willmcvicker: squash with commit 0c0d417747d8e289b2808c3fca32c845f82fd5e5]

    Will McVicker
     

22 Jun, 2020

1 commit


19 May, 2020

1 commit


09 Apr, 2020

1 commit


31 Mar, 2020

1 commit


20 Feb, 2020

1 commit


27 Nov, 2019

1 commit


21 Nov, 2019

1 commit


15 Nov, 2019

1 commit


26 Oct, 2019

1 commit

  • We've been building mainline x86_64 with LLD for months now, and don't
    plan to upgrade Android's binutils to work around issues upstream
    related to:

    commit c603a309cc75 ("x86/mm: Identify the end of the kernel area to be reserved")

    Bug: 138463564
    Signed-off-by: Nick Desaulniers
    Signed-off-by: Alistair Delva
    Change-Id: Ic52f7f374c494e5d39efb758a7739ebd33799f49

    Nick Desaulniers
     

23 Oct, 2019

1 commit


30 Aug, 2019

1 commit