From: Ard Biesheuvel <ardb@kernel.org>
To: info@kernelci.org
Subject: Re: efi/urgent build: 3 builds: 0 failed, 3 passed (efi-urgent-for-v5.14-rc2-2-g5bb60b28ce5be)
Date: Fri, 23 Jul 2021 16:22:02 +0200 [thread overview]
Message-ID: <CAMj1kXFtZjTKOifJUMSiVkJ2hi7u5YZVnCWZ76TdaLYbAb2Mjg@mail.gmail.com> (raw)
In-Reply-To: <60f9c3b4.1c69fb81.7d558.2406@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 1272 bytes --]
Hello all,
Please see the report below: this used to list 4 configs that are tested
with my EFI branches, but for some reason, arm64 is no longer included.
Could this be reverted please?
Thanks,
Ard.
On Thu, 22 Jul 2021 at 21:15, kernelci.org bot <bot@kernelci.org> wrote:
> *efi/urgent build: 3 builds: 0 failed, 3 passed
> (efi-urgent-for-v5.14-rc2-2-g5bb60b28ce5be)*
> Full Build Summary:
> https://kernelci.org/build/efi/branch/urgent/kernel/efi-urgent-for-v5.14-rc2-2-g5bb60b28ce5be/
> Tree: efi
> Branch: urgent
> Git Describe: efi-urgent-for-v5.14-rc2-2-g5bb60b28ce5be
> Git Commit: 5bb60b28ce5bee48838c3fdc667c7247e722b34d
> Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git
> <https://git.kernel.org/cgit/linux/kernel/git/efi/efi.git/commit/?id=5bb60b28ce5bee48838c3fdc667c7247e722b34d>
> Built: 3 unique architectures
>
> *Detailed per-defconfig build reports:*
>
> *i386_defconfig* (i386, gcc-8) — PASS, 0 errors, 0 warnings, 0 section
> mismatches
>
> *multi_v7_defconfig* (arm, gcc-8) — PASS, 0 errors, 0 warnings, 0 section
> mismatches
>
> *x86_64_defconfig* (x86_64, gcc-8) — PASS, 0 errors, 0 warnings, 0
> section mismatches
>
> ─
> For more info write to <info@kernelci.org>
>
[-- Attachment #2: Type: text/html, Size: 2748 bytes --]
next parent reply other threads:[~2021-07-23 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <60f9c3b4.1c69fb81.7d558.2406@mx.google.com>
2021-07-23 14:22 ` Ard Biesheuvel [this message]
2021-07-23 18:07 ` efi/urgent build: 3 builds: 0 failed, 3 passed (efi-urgent-for-v5.14-rc2-2-g5bb60b28ce5be) Guillaume Tucker
2021-07-26 13:57 ` Ard Biesheuvel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMj1kXFtZjTKOifJUMSiVkJ2hi7u5YZVnCWZ76TdaLYbAb2Mjg@mail.gmail.com \
--to=ardb@kernel.org \
--cc=info@kernelci.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).