From: Christian Brauner <christian.brauner@ubuntu.com>
To: shuah <shuah@kernel.org>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
bgolaszewski@baylibre.com, Daniel Borkmann <daniel@iogearbox.net>,
bpf <bpf@vger.kernel.org>, Networking <netdev@vger.kernel.org>
Subject: Re: Linux 5.4 kselftest known issues - update
Date: Fri, 4 Oct 2019 11:43:19 +0200 [thread overview]
Message-ID: <20191004094318.3gzcfpr6kdj76pll@wittgenstein> (raw)
In-Reply-To: <2a835150-d7f1-1c4a-80cb-d385f799dd14@kernel.org>
On Thu, Oct 03, 2019 at 08:30:55AM -0600, shuah wrote:
> On 9/26/19 11:41 AM, Shuah Khan wrote:
> > Here are the know kselftest issues on Linux 5.4 with
> > top commit commit 619e17cf75dd58905aa67ccd494a6ba5f19d6cc6
> > on x86_64:
> >
> > The goal is to get these addressed before 5.4 comes out.
>
> All of these issues are now fixed, except the bpf llvm dependency.
> These fixes should all be in linux-next if they haven't already.
>
> >
> > 3 build failures and status:
> >
> > pidfd - undefined reference to `pthread_create' collect2: error: ld
> > returned 1 exit status
> >
> > Fixed: https://patchwork.kernel.org/patch/11159517/
This commit is included in the following pr which I sent just now:
https://lore.kernel.org/r/20191004093947.14471-1-christian.brauner@ubuntu.com
Thanks!
Christian
prev parent reply other threads:[~2019-10-04 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 17:41 Linux 5.4 kselftest known issues Shuah Khan
2019-10-03 14:30 ` Linux 5.4 kselftest known issues - update shuah
2019-10-04 9:43 ` Christian Brauner [this message]
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=20191004094318.3gzcfpr6kdj76pll@wittgenstein \
--to=christian.brauner@ubuntu.com \
--cc=bgolaszewski@baylibre.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kvm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.org \
--cc=skhan@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 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.