From: Alexei Starovoitov <ast@plumgrid.com>
To: Guenter Roeck <linux@roeck-us.net>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Marc Zyngier <marc.zyngier@arm.com>,
"pi-cheng.chen" <pi-cheng.chen@linaro.org>
Subject: Re: linux-next: Tree for Aug 31 (new arm, arm64, s390 failures)
Date: Mon, 31 Aug 2015 08:09:02 -0700 [thread overview]
Message-ID: <55E46E0E.1040007@plumgrid.com> (raw)
In-Reply-To: <20150831141736.GA19616@roeck-us.net>
On 8/31/15 7:17 AM, Guenter Roeck wrote:
> s390:
>
> kernel/built-in.o: In function `bpf_trace_printk':
> bpf_trace.c:(.text+0x116a5c): undefined reference to `strncpy_from_unsafe'
> kernel/built-in.o: In function `fetch_memory_string':
> trace_kprobe.c:(.text+0x118ee0): undefined reference to `strncpy_from_unsafe'
>
> Appears to be due to 'bpf: add support for %s specifier to bpf_trace_printk()'.
working on a fix...
next prev parent reply other threads:[~2015-08-31 15:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 9:54 linux-next: Tree for Aug 31 Stephen Rothwell
2015-08-31 14:17 ` linux-next: Tree for Aug 31 (new arm, arm64, s390 failures) Guenter Roeck
2015-08-31 15:09 ` Alexei Starovoitov [this message]
2015-08-31 15:31 ` Marc Zyngier
2015-08-31 15:31 ` Marc Zyngier
2015-08-31 15:47 ` Guenter Roeck
2015-08-31 16:18 ` Marc Zyngier
2015-08-31 16:18 ` Marc Zyngier
2015-08-31 16:40 ` Guenter Roeck
2015-08-31 17:09 ` Marc Zyngier
2015-08-31 17:09 ` Marc Zyngier
2015-08-31 18:26 ` Marc Zyngier
2015-08-31 18:26 ` Marc Zyngier
2015-08-31 18:57 ` Guenter Roeck
2015-08-31 19:13 ` Marc Zyngier
2015-08-31 19:13 ` Marc Zyngier
2015-08-31 19:40 ` Guenter Roeck
2015-08-31 20:07 ` Mark Brown
2015-08-31 18:33 ` 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=55E46E0E.1040007@plumgrid.com \
--to=ast@plumgrid.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=marc.zyngier@arm.com \
--cc=pi-cheng.chen@linaro.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 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.