linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Andrii Nakryiko" <andrii.nakryiko@gmail.com>,
	"Andrii Nakryiko" <andriin@fb.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	BPF-dev-list <bpf@vger.kernel.org>,
	"Alexei Starovoitov" <alexei.starovoitov@gmail.com>,
	"Daniel Borkmann" <borkmann@iogearbox.net>,
	"David Miller" <davem@davemloft.net>,
	LKML <linux-kernel@vger.kernel.org>,
	"Anders Roxell" <anders.roxell@linaro.org>,
	"Toke Høiland-Jørgensen" <toke@redhat.com>,
	brouer@redhat.com
Subject: Re: Kernel 5.5.4 build fail for BPF-selftests with latest LLVM
Date: Wed, 19 Feb 2020 20:40:39 +0100	[thread overview]
Message-ID: <20200219204039.121f10d2@carbon> (raw)
In-Reply-To: <20200219181250.GA2852230@kroah.com>

On Wed, 19 Feb 2020 19:12:50 +0100
Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:

> On Wed, Feb 19, 2020 at 02:42:54PM +0100, Jesper Dangaard Brouer wrote:
> > On Wed, 19 Feb 2020 14:28:56 +0100
> > Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> >   
> > > On Wed, Feb 19, 2020 at 01:30:12PM +0100, Jesper Dangaard Brouer wrote:  
> > > > Hi Andrii,
> > > > 
> > > > Downloaded tarball for kernel release 5.5.4, and I cannot compile
> > > > tools/testing/selftests/bpf/ with latest LLVM release version 9.    
> > > 
[...]
> > > And has llvm 9 always worked here?  
> > 
> > Yes, llvm-9 used to work for tools/testing/selftests/bpf/.  
> 
> As of when?

Kernel v5.4 works when compiling BPF-selftests with LLVM 9.0.1.

-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Principal Kernel Engineer at Red Hat
  LinkedIn: http://www.linkedin.com/in/brouer


  reply	other threads:[~2020-02-19 19:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19 12:30 Kernel 5.5.4 build fail for BPF-selftests with latest LLVM Jesper Dangaard Brouer
2020-02-19 13:28 ` Greg Kroah-Hartman
2020-02-19 13:42   ` Jesper Dangaard Brouer
2020-02-19 18:12     ` Greg Kroah-Hartman
2020-02-19 19:40       ` Jesper Dangaard Brouer [this message]
2020-02-19 20:20         ` Greg Kroah-Hartman
2020-02-19 16:41 ` Alexei Starovoitov
2020-02-19 17:03   ` Jesper Dangaard Brouer
2020-02-19 17:38     ` Andrii Nakryiko
2020-02-19 18:28       ` Jesper Dangaard Brouer
2020-02-19 18:38         ` Andrii Nakryiko
2020-02-19 20:06           ` Jesper Dangaard Brouer
2020-02-19 21:59             ` Daniel Díaz
2020-02-19 22:26               ` Andrii Nakryiko
2020-02-20  0:27               ` Alexei Starovoitov
2020-02-20  0:47                 ` shuah
2020-02-20 16:37                   ` Jesper Dangaard Brouer
2020-02-20 17:02                     ` Bird, Tim
2020-02-20 17:26                       ` Alexei Starovoitov
2020-02-20 17:41                         ` Bird, Tim
2020-02-20 19:18                           ` Alexei Starovoitov

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=20200219204039.121f10d2@carbon \
    --to=brouer@redhat.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=anders.roxell@linaro.org \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andriin@fb.com \
    --cc=borkmann@iogearbox.net \
    --cc=bpf@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=toke@redhat.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 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 NNTP newsgroup(s).