From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/kmod: bump version to 28
Date: Wed, 20 Jan 2021 22:10:18 +0100 [thread overview]
Message-ID: <YAicOnyPw2WKMsSW@pevik> (raw)
In-Reply-To: <20210120202210.2832-1-petr.vorel@gmail.com>
Hi,
tested:
andes-nds32 [ 1/45]: OK
arm-aarch64 [ 2/45]: OK
bootlin-x86-64-glibc [ 3/45]: OK
br-aarch64-glibc [ 4/45]: OK
br-arcle-hs38 [ 5/45]: OK
br-arm-basic [ 6/45]: OK
br-arm-cortex-a9-glibc [ 7/45]: OK
br-arm-cortex-a9-musl [ 8/45]: OK
br-arm-cortex-m4-full [ 9/45]: SKIPPED
br-arm-full [10/45]: OK
br-arm-full-nothread [11/45]: OK
br-arm-full-static [12/45]: SKIPPED
br-i386-pentium-mmx-musl [13/45]: OK
br-i386-pentium4-full [14/45]: OK
br-microblazeel-full [15/45]: OK
br-mipsel-o32-full [16/45]: OK
br-mips32r6-el-hf-glibc [17/45]: OK
br-mips64-n64-full [18/45]: OK
br-mips64r6-el-hf-glibc [19/45]: OK
br-m68k-5208-full [20/45]: SKIPPED
br-m68k-68040-full [21/45]: OK
br-nios2-glibc [22/45]: OK
br-openrisc-uclibc [23/45]: OK
br-powerpc-e500mc-full [24/45]: OK
br-powerpc-603e-basic-cpp [25/45]: OK
br-powerpc64le-power8-glibc [26/45]: OK
br-powerpc64-power7-glibc [27/45]: OK
br-riscv32 [28/45]: OK
br-riscv64 [29/45]: OK
br-riscv64-musl [30/45]: OK
br-sh4-full [31/45]: OK
br-sparc-uclibc [32/45]: OK
br-sparc64-glibc [33/45]: OK
br-xtensa-full [34/45]: OK
br-x86-64-core2-full [35/45]: OK
br-x86-64-musl [36/45]: OK
linaro-aarch64-be [37/45]: OK
linaro-aarch64 [38/45]: OK
linaro-arm [39/45]: OK
sourcery-arm-armv4t [40/45]: OK
sourcery-arm [41/45]: OK
sourcery-arm-thumb2 [42/45]: OK
sourcery-mips [43/45]: OK
sourcery-mips64 [44/45]: OK
sourcery-nios2 [45/45]: OK
45 builds, 3 skipped, 0 build failed, 0 legal-info failed
Kind regards,
Petr
next prev parent reply other threads:[~2021-01-20 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 20:22 [Buildroot] [PATCH 1/1] package/kmod: bump version to 28 Petr Vorel
2021-01-20 21:10 ` Petr Vorel [this message]
2021-01-21 20:41 ` Thomas Petazzoni
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=YAicOnyPw2WKMsSW@pevik \
--to=petr.vorel@gmail.com \
--cc=buildroot@busybox.net \
/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