From: kernel test robot <lkp@intel.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: [wireless-next:main] BUILD SUCCESS 5ad8897fd15a3716601509ed4a7bc47bf0cab661
Date: Wed, 19 Jun 2024 21:16:02 +0800 [thread overview]
Message-ID: <202406192158.DU3kCSyd-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git main
branch HEAD: 5ad8897fd15a3716601509ed4a7bc47bf0cab661 wifi: wilc1000: disable SDIO func IRQ before suspend
elapsed time: 1533m
configs tested: 59
configs skipped: 0
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
arc randconfig-001-20240619 gcc-13.2.0
arc randconfig-002-20240619 gcc-13.2.0
arm randconfig-001-20240619 clang-19
arm randconfig-002-20240619 clang-19
arm randconfig-003-20240619 clang-19
arm randconfig-004-20240619 gcc-13.2.0
arm64 randconfig-001-20240619 clang-19
arm64 randconfig-002-20240619 clang-19
arm64 randconfig-003-20240619 clang-19
arm64 randconfig-004-20240619 clang-19
csky randconfig-001-20240619 gcc-13.2.0
csky randconfig-002-20240619 gcc-13.2.0
hexagon randconfig-001-20240619 clang-15
hexagon randconfig-002-20240619 clang-19
i386 buildonly-randconfig-001-20240619 clang-18
i386 buildonly-randconfig-002-20240619 clang-18
i386 buildonly-randconfig-003-20240619 clang-18
i386 buildonly-randconfig-004-20240619 clang-18
i386 buildonly-randconfig-005-20240619 gcc-7
i386 buildonly-randconfig-006-20240619 gcc-7
i386 randconfig-001-20240619 gcc-7
i386 randconfig-002-20240619 gcc-7
i386 randconfig-003-20240619 clang-18
i386 randconfig-004-20240619 gcc-7
i386 randconfig-005-20240619 clang-18
i386 randconfig-006-20240619 gcc-9
i386 randconfig-011-20240619 clang-18
i386 randconfig-012-20240619 clang-18
i386 randconfig-013-20240619 gcc-13
i386 randconfig-014-20240619 clang-18
i386 randconfig-015-20240619 clang-18
i386 randconfig-016-20240619 gcc-13
loongarch randconfig-001-20240619 gcc-13.2.0
loongarch randconfig-002-20240619 gcc-13.2.0
nios2 randconfig-001-20240619 gcc-13.2.0
x86_64 buildonly-randconfig-001-20240619 clang-18
x86_64 buildonly-randconfig-002-20240619 clang-18
x86_64 buildonly-randconfig-003-20240619 gcc-11
x86_64 buildonly-randconfig-004-20240619 clang-18
x86_64 buildonly-randconfig-005-20240619 clang-18
x86_64 buildonly-randconfig-006-20240619 gcc-13
x86_64 randconfig-001-20240619 gcc-13
x86_64 randconfig-002-20240619 clang-18
x86_64 randconfig-003-20240619 gcc-8
x86_64 randconfig-004-20240619 clang-18
x86_64 randconfig-005-20240619 clang-18
x86_64 randconfig-006-20240619 gcc-13
x86_64 randconfig-011-20240619 gcc-13
x86_64 randconfig-012-20240619 gcc-13
x86_64 randconfig-013-20240619 gcc-13
x86_64 randconfig-014-20240619 clang-18
x86_64 randconfig-015-20240619 clang-18
x86_64 randconfig-016-20240619 gcc-11
x86_64 randconfig-071-20240619 clang-18
x86_64 randconfig-072-20240619 clang-18
x86_64 randconfig-073-20240619 gcc-9
x86_64 randconfig-074-20240619 gcc-9
x86_64 randconfig-075-20240619 clang-18
x86_64 randconfig-076-20240619 clang-18
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-06-19 13:17 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=202406192158.DU3kCSyd-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 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 NNTP newsgroup(s).