public inbox for ath12k@lists.infradead.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: Kalle Valo <kvalo@kernel.org>, ath12k@lists.infradead.org
Subject: [ath:master] BUILD SUCCESS 0ea161de5e5afa1323e982adc8f59bf4af99a84b
Date: Thu, 14 Nov 2024 14:16:43 +0800	[thread overview]
Message-ID: <202411141434.b7fttIpb-lkp@intel.com> (raw)

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git master
branch HEAD: 0ea161de5e5afa1323e982adc8f59bf4af99a84b  Add localversion-wireless-testing-ath

elapsed time: 737m

configs tested: 52
configs skipped: 1

The following configs have been built successfully.
More configs may be tested in the coming days.

tested configs:
alpha              allyesconfig    clang-20
arc                allmodconfig    clang-20
arc                allmodconfig    gcc-13.2.0
arc                allyesconfig    clang-20
arc                allyesconfig    gcc-13.2.0
arm                allmodconfig    clang-20
arm                allmodconfig    gcc-14.2.0
arm                allyesconfig    clang-20
arm                allyesconfig    gcc-14.2.0
arm64              allmodconfig    clang-20
hexagon            allmodconfig    clang-20
hexagon            allyesconfig    clang-20
i386               allmodconfig    clang-19
i386               allmodconfig    gcc-12
i386                allnoconfig    clang-19
i386                allnoconfig    gcc-12
i386               allyesconfig    clang-19
i386               allyesconfig    gcc-12
i386                  defconfig    clang-19
loongarch          allmodconfig    gcc-14.2.0
m68k               allmodconfig    gcc-14.2.0
m68k               allyesconfig    gcc-14.2.0
microblaze         allmodconfig    gcc-14.2.0
microblaze         allyesconfig    gcc-14.2.0
openrisc            allnoconfig    gcc-14.2.0
openrisc           allyesconfig    gcc-14.2.0
parisc             allmodconfig    gcc-14.2.0
parisc              allnoconfig    gcc-14.2.0
parisc             allyesconfig    gcc-14.2.0
powerpc            allmodconfig    gcc-14.2.0
powerpc             allnoconfig    gcc-14.2.0
powerpc            allyesconfig    gcc-14.2.0
riscv              allmodconfig    gcc-14.2.0
riscv               allnoconfig    gcc-14.2.0
riscv              allyesconfig    gcc-14.2.0
s390               allmodconfig    clang-20
s390               allmodconfig    gcc-14.2.0
s390                allnoconfig    clang-20
s390               allyesconfig    gcc-14.2.0
sh                 allmodconfig    gcc-14.2.0
sh                 allyesconfig    gcc-14.2.0
sparc              allmodconfig    gcc-14.2.0
um                 allmodconfig    clang-20
um                  allnoconfig    clang-17
um                 allyesconfig    clang-20
x86_64              allnoconfig    clang-19
x86_64             allyesconfig    clang-19
x86_64                defconfig    clang-19
x86_64                defconfig    gcc-11
x86_64                    kexec    clang-19
x86_64                 rhel-8.3    gcc-12
x86_64      rhel-8.3-kselftests    clang-19

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


                 reply	other threads:[~2024-11-14  7:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202411141434.b7fttIpb-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ath12k@lists.infradead.org \
    --cc=kvalo@kernel.org \
    --cc=quic_jjohnson@quicinc.com \
    /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