From: kernel test robot <lkp@intel.com>
To: Johannes Berg <johannes.berg@intel.com>
Cc: Kalle Valo <kvalo@kernel.org>, linux-wireless@vger.kernel.org
Subject: [wireless:for-next] BUILD SUCCESS bcbc84af1183c8cf3d1ca9b78540c2185cd85e7f
Date: Sat, 20 Jan 2024 06:42:28 +0800 [thread overview]
Message-ID: <202401200625.Jun3FRzP-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git for-next
branch HEAD: bcbc84af1183c8cf3d1ca9b78540c2185cd85e7f wifi: mac80211: fix race condition on enabling fast-xmit
elapsed time: 1895m
configs tested: 65
configs skipped: 0
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
arc randconfig-001-20240120 gcc
arc randconfig-002-20240120 gcc
arm randconfig-001-20240120 clang
arm randconfig-002-20240120 clang
arm randconfig-003-20240120 clang
arm randconfig-004-20240120 clang
arm64 randconfig-001-20240120 clang
arm64 randconfig-002-20240120 clang
arm64 randconfig-003-20240120 clang
arm64 randconfig-004-20240120 clang
csky randconfig-001-20240120 gcc
csky randconfig-002-20240120 gcc
hexagon randconfig-001-20240120 clang
hexagon randconfig-002-20240120 clang
i386 buildonly-randconfig-001-20240119 gcc
i386 buildonly-randconfig-002-20240119 gcc
i386 buildonly-randconfig-003-20240119 gcc
i386 buildonly-randconfig-004-20240119 gcc
i386 buildonly-randconfig-005-20240119 gcc
i386 buildonly-randconfig-006-20240119 gcc
i386 randconfig-001-20240119 gcc
i386 randconfig-002-20240119 gcc
i386 randconfig-003-20240119 gcc
i386 randconfig-004-20240119 gcc
i386 randconfig-005-20240119 gcc
i386 randconfig-006-20240119 gcc
i386 randconfig-011-20240119 clang
i386 randconfig-012-20240119 clang
i386 randconfig-013-20240119 clang
i386 randconfig-014-20240119 clang
i386 randconfig-015-20240119 clang
i386 randconfig-016-20240119 clang
loongarch randconfig-001-20240120 gcc
loongarch randconfig-002-20240120 gcc
nios2 randconfig-001-20240120 gcc
nios2 randconfig-002-20240120 gcc
parisc randconfig-001-20240120 gcc
parisc randconfig-002-20240120 gcc
powerpc randconfig-001-20240120 clang
powerpc randconfig-002-20240120 clang
powerpc randconfig-003-20240120 clang
x86_64 buildonly-randconfig-001-20240120 clang
x86_64 buildonly-randconfig-002-20240120 clang
x86_64 buildonly-randconfig-003-20240120 clang
x86_64 buildonly-randconfig-004-20240120 clang
x86_64 buildonly-randconfig-005-20240120 clang
x86_64 buildonly-randconfig-006-20240120 clang
x86_64 randconfig-001-20240120 gcc
x86_64 randconfig-002-20240120 gcc
x86_64 randconfig-003-20240120 gcc
x86_64 randconfig-004-20240120 gcc
x86_64 randconfig-005-20240120 gcc
x86_64 randconfig-006-20240120 gcc
x86_64 randconfig-011-20240120 clang
x86_64 randconfig-012-20240120 clang
x86_64 randconfig-013-20240120 clang
x86_64 randconfig-014-20240120 clang
x86_64 randconfig-015-20240120 clang
x86_64 randconfig-016-20240120 clang
x86_64 randconfig-071-20240120 clang
x86_64 randconfig-072-20240120 clang
x86_64 randconfig-073-20240120 clang
x86_64 randconfig-074-20240120 clang
x86_64 randconfig-075-20240120 clang
x86_64 randconfig-076-20240120 clang
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-19 22:43 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=202401200625.Jun3FRzP-lkp@intel.com \
--to=lkp@intel.com \
--cc=johannes.berg@intel.com \
--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).