From: kbuild test robot <lkp@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [jkirsher-net-queue:dev-queue] BUILD SUCCESS d4307953a0e026b629193b8d86ccdefbc9f59348
Date: Fri, 13 Jul 2018 01:41:14 +0800 [thread overview]
Message-ID: <5b4792ba.ov1ueakO2+PAqK7s%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/net-queue.git dev-queue
branch HEAD: d4307953a0e026b629193b8d86ccdefbc9f59348 ixgbe: Off by one in ixgbe_ipsec_tx()
elapsed time: 9m
configs tested: 82
The following configs have been built successfully.
More configs may be tested in the coming days.
sh allnoconfig
sh rsk7269_defconfig
sh sh7785lcr_32bit_defconfig
sh titan_defconfig
i386 randconfig-x016-201827
i386 randconfig-x017-201827
i386 randconfig-x014-201827
i386 randconfig-x012-201827
i386 randconfig-x018-201827
i386 randconfig-x011-201827
i386 randconfig-x013-201827
i386 randconfig-x019-201827
i386 randconfig-x015-201827
i386 randconfig-x010-201827
i386 randconfig-n0-201827
powerpc allnoconfig
powerpc defconfig
powerpc ppc64_defconfig
s390 default_defconfig
x86_64 randconfig-x015-201827
x86_64 randconfig-x011-201827
x86_64 randconfig-x018-201827
x86_64 randconfig-x010-201827
x86_64 randconfig-x014-201827
x86_64 randconfig-x019-201827
x86_64 randconfig-x017-201827
x86_64 randconfig-x016-201827
x86_64 randconfig-x013-201827
x86_64 randconfig-x012-201827
ia64 alldefconfig
ia64 allnoconfig
ia64 defconfig
openrisc or1ksim_defconfig
um i386_defconfig
um x86_64_defconfig
alpha defconfig
parisc allnoconfig
parisc b180_defconfig
parisc c3000_defconfig
parisc defconfig
i386 randconfig-s0-201827
i386 randconfig-s1-201827
i386 randconfig-x009-201827
i386 randconfig-x008-201827
i386 randconfig-x001-201827
i386 randconfig-x000-201827
i386 randconfig-x003-201827
i386 randconfig-x005-201827
i386 randconfig-x006-201827
i386 randconfig-x004-201827
i386 randconfig-x002-201827
i386 randconfig-x007-201827
microblaze mmu_defconfig
microblaze nommu_defconfig
sparc defconfig
sparc64 allnoconfig
sparc64 defconfig
c6x evmc6678_defconfig
h8300 h8300h-sim_defconfig
nios2 10m50_defconfig
xtensa common_defconfig
xtensa iss_defconfig
x86_64 randconfig-x003-201827
x86_64 randconfig-x007-201827
x86_64 randconfig-x004-201827
x86_64 randconfig-x005-201827
x86_64 randconfig-x000-201827
x86_64 randconfig-x001-201827
x86_64 randconfig-x008-201827
x86_64 randconfig-x006-201827
x86_64 randconfig-x002-201827
x86_64 randconfig-x009-201827
i386 randconfig-x078-201827
i386 randconfig-x079-201827
i386 randconfig-x074-201827
i386 randconfig-x075-201827
i386 randconfig-x076-201827
i386 randconfig-x070-201827
i386 randconfig-x073-201827
i386 randconfig-x071-201827
i386 randconfig-x077-201827
i386 randconfig-x072-201827
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next reply other threads:[~2018-07-12 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 17:41 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-13 21:32 [Intel-wired-lan] [jkirsher-net-queue:dev-queue] BUILD SUCCESS d4307953a0e026b629193b8d86ccdefbc9f59348 kbuild test robot
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=5b4792ba.ov1ueakO2+PAqK7s%lkp@intel.com \
--to=lkp@intel.com \
--cc=intel-wired-lan@osuosl.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