All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Will Deacon <will.deacon@arm.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Build/qemu test results for v4.18-rc2
Date: Mon, 25 Jun 2018 15:17:47 +0800	[thread overview]
Message-ID: <CA+55aFzhE2PQOM-pykY=GammunCLYhY37eS_UiYnXWXuSvHLZQ@mail.gmail.com> (raw)
In-Reply-To: <0ecc33a4-60c0-f978-f281-99844508d09a@roeck-us.net>

On Mon, Jun 25, 2018 at 12:25 AM Guenter Roeck <linux@roeck-us.net> wrote:
>
> Build results:
>         total: 134 pass: 113 fail: 21
> Failed builds:
>         i386:allyesconfig
>         i386:allmodconfig

These seem to be due to the trial code to embed user modules in the
netfilter modules to use bpf  to do netfilter (aka bpfilter). Right
now that doesn't cross-compile right.

I'm hoping the networking people get their trial balloon to work
right, but if worst comes to worst, it will just be disabled for 4.18.

In the meantime, I'm hoping it doesn't hold back any *other* testing.
I'm assuming the allyes/modconfig build failures don't actually matter
for the boot testing etc.

The mips problems I have no idea about.

             Linus

  reply	other threads:[~2018-06-25  7:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-24 16:25 Build/qemu test results for v4.18-rc2 Guenter Roeck
2018-06-25  7:17 ` Linus Torvalds [this message]
2018-06-25  8:40   ` Thomas Gleixner
2018-06-25 16:31   ` Guenter Roeck
2018-06-26 15:40     ` Linus Torvalds
2018-06-27 15:27       ` Linus Torvalds
2018-06-27 16:30         ` Guenter Roeck

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='CA+55aFzhE2PQOM-pykY=GammunCLYhY37eS_UiYnXWXuSvHLZQ@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=tglx@linutronix.de \
    --cc=will.deacon@arm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.