mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	bpf@vger.kernel.org,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	kpsingh@chromium.org
Subject: Re: linux-next: Tree for Mar 30 (bpf)
Date: Mon, 30 Mar 2020 19:25:35 +0200	[thread overview]
Message-ID: <d5b4bd95-7ef9-58cb-1955-900e6edb2467@iogearbox.net> (raw)
In-Reply-To: <86f7031a-57c6-5d50-2788-ae0e06a7c138@infradead.org>

[Cc KP, ptal]

On 3/30/20 7:15 PM, Randy Dunlap wrote:
> On 3/30/20 2:43 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> The merge window has opened, so please do not add any material for the
>> next release into your linux-next included trees/branches until after
>> the merge window closes.
>>
>> Changes since 20200327:
> 
> (note: linux-next is based on linux 5.6-rc7)
> 
> 
> on i386:
> 
> ld: kernel/bpf/bpf_lsm.o:(.rodata+0x0): undefined reference to `bpf_tracing_func_proto'
> 
> 
> Full randconfig file is attached.
> 


  reply	other threads:[~2020-03-30 17:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-30  9:43 linux-next: Tree for Mar 30 Stephen Rothwell
2020-03-30 17:15 ` linux-next: Tree for Mar 30 (bpf) Randy Dunlap
2020-03-30 17:25   ` Daniel Borkmann [this message]
2020-03-30 17:54     ` KP Singh
2020-03-30 18:05       ` KP Singh
2020-03-30 18:15         ` Randy Dunlap
2020-03-30 18:49         ` KP Singh
2020-03-30 17:22 ` linux-next: Tree for Mar 30 (vhost) Randy Dunlap
2020-03-31  2:27   ` Jason Wang
2020-03-31 13:13     ` Michael S. Tsirkin
2020-03-31 13:11   ` Michael S. Tsirkin

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=d5b4bd95-7ef9-58cb-1955-900e6edb2467@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=bpf@vger.kernel.org \
    --cc=kpsingh@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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

all inboxes | Powered by JetHome®