From: kernel test robot <lkp@intel.com>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org
Subject: [staging:staging-testing] BUILD SUCCESS cc59bde1c920ab6689d40eba1a6fcd4edbec2455
Date: Thu, 29 Jul 2021 14:31:37 +0800 [thread overview]
Message-ID: <61024b49.6GlqTtb08ae1a3GN%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git staging-testing
branch HEAD: cc59bde1c920ab6689d40eba1a6fcd4edbec2455 staging: sm750fb: Rename vScreen to v_screen in lynxfb_crtc
elapsed time: 722m
configs tested: 100
configs skipped: 4
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
arm defconfig
arm64 allyesconfig
arm64 defconfig
arm allyesconfig
arm allmodconfig
i386 randconfig-c001-20210728
mips tb0219_defconfig
powerpc socrates_defconfig
mips db1xxx_defconfig
m68k atari_defconfig
sh espt_defconfig
powerpc asp8347_defconfig
powerpc sam440ep_defconfig
powerpc mpc866_ads_defconfig
m68k m5407c3_defconfig
arc nsimosci_hs_smp_defconfig
mips e55_defconfig
m68k multi_defconfig
mips cu1830-neo_defconfig
sh rsk7264_defconfig
sh se7751_defconfig
openrisc defconfig
parisc defconfig
powerpc ppc64_defconfig
xtensa defconfig
sh hp6xx_defconfig
sh r7780mp_defconfig
sh se7343_defconfig
powerpc mpc512x_defconfig
x86_64 allnoconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
nds32 defconfig
nios2 allyesconfig
csky defconfig
alpha defconfig
alpha allyesconfig
xtensa allyesconfig
h8300 allyesconfig
arc defconfig
sh allmodconfig
s390 allyesconfig
s390 allmodconfig
parisc allyesconfig
s390 defconfig
i386 allyesconfig
sparc allyesconfig
sparc defconfig
i386 defconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a006-20210728
x86_64 randconfig-a003-20210728
x86_64 randconfig-a001-20210728
x86_64 randconfig-a004-20210728
x86_64 randconfig-a005-20210728
x86_64 randconfig-a002-20210728
i386 randconfig-a005-20210728
i386 randconfig-a003-20210728
i386 randconfig-a004-20210728
i386 randconfig-a002-20210728
i386 randconfig-a001-20210728
i386 randconfig-a006-20210728
i386 randconfig-a016-20210728
i386 randconfig-a012-20210728
i386 randconfig-a013-20210728
i386 randconfig-a014-20210728
i386 randconfig-a011-20210728
i386 randconfig-a015-20210728
riscv nommu_k210_defconfig
riscv allyesconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv defconfig
riscv rv32_defconfig
riscv allmodconfig
x86_64 rhel-8.3-kselftests
um x86_64_defconfig
um i386_defconfig
x86_64 allyesconfig
x86_64 defconfig
x86_64 rhel-8.3
x86_64 kexec
clang tested configs:
x86_64 randconfig-c001-20210728
x86_64 randconfig-a016-20210728
x86_64 randconfig-a011-20210728
x86_64 randconfig-a014-20210728
x86_64 randconfig-a013-20210728
x86_64 randconfig-a012-20210728
x86_64 randconfig-a015-20210728
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
reply other threads:[~2021-07-29 6:32 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=61024b49.6GlqTtb08ae1a3GN%lkp@intel.com \
--to=lkp@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.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).