From: kernel test robot <lkp@intel.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: linux-wireless@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>
Subject: [wireless-next:main] BUILD SUCCESS a1d0b9535cd8ce6f6c6870fcac1760cbaafc0f48
Date: Thu, 17 Nov 2022 06:57:47 +0800 [thread overview]
Message-ID: <63756aeb.JD6Lrym3eKTO6Zij%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git main
branch HEAD: a1d0b9535cd8ce6f6c6870fcac1760cbaafc0f48 wifi: wl1251: switch to using gpiod API
elapsed time: 726m
configs tested: 58
configs skipped: 2
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
alpha defconfig
arc defconfig
um i386_defconfig
um x86_64_defconfig
s390 allmodconfig
s390 defconfig
sh allmodconfig
powerpc allnoconfig
m68k allmodconfig
alpha allyesconfig
arc allyesconfig
m68k allyesconfig
x86_64 defconfig
s390 allyesconfig
x86_64 rhel-8.3
x86_64 allyesconfig
mips allyesconfig
powerpc allmodconfig
x86_64 rhel-8.3-kselftests
x86_64 rhel-8.3-func
ia64 allmodconfig
i386 defconfig
x86_64 randconfig-a013
x86_64 randconfig-a015
i386 randconfig-a001
i386 randconfig-a014
i386 randconfig-a003
x86_64 rhel-8.3-syz
x86_64 rhel-8.3-kunit
arc randconfig-r043-20221116
x86_64 rhel-8.3-kvm
i386 randconfig-a016
i386 randconfig-a005
x86_64 randconfig-a004
arm defconfig
x86_64 randconfig-a002
i386 randconfig-a012
x86_64 randconfig-a006
x86_64 randconfig-a011
arm64 allyesconfig
arm allyesconfig
i386 allyesconfig
clang tested configs:
i386 randconfig-a013
i386 randconfig-a015
x86_64 randconfig-a014
i386 randconfig-a002
i386 randconfig-a004
hexagon randconfig-r041-20221116
hexagon randconfig-r045-20221116
x86_64 randconfig-a001
i386 randconfig-a006
riscv randconfig-r042-20221116
x86_64 randconfig-a003
i386 randconfig-a011
x86_64 randconfig-a005
s390 randconfig-r044-20221116
x86_64 randconfig-a016
x86_64 randconfig-a012
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-11-16 22:58 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=63756aeb.JD6Lrym3eKTO6Zij%lkp@intel.com \
--to=lkp@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.