From: David Miller <davem@davemloft.net>
To: akpm@linux-foundation.org
Cc: netdev@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net
Subject: Re: [patch 1/1] kernel/trace/bpf_trace.c: work around gcc-4.4.4 anon union initialization bug
Date: Tue, 19 Jul 2016 19:28:01 -0700 (PDT) [thread overview]
Message-ID: <20160719.192801.35741043299529276.davem@davemloft.net> (raw)
In-Reply-To: <578d5d52.lh08e3GTSq3vxxIL%akpm@linux-foundation.org>
From: akpm@linux-foundation.org
Date: Mon, 18 Jul 2016 15:50:58 -0700
> From: Andrew Morton <akpm@linux-foundation.org>
> Subject: kernel/trace/bpf_trace.c: work around gcc-4.4.4 anon union initialization bug
>
> kernel/trace/bpf_trace.c: In function 'bpf_event_output':
> kernel/trace/bpf_trace.c:312: error: unknown field 'next' specified in initializer
> kernel/trace/bpf_trace.c:312: warning: missing braces around initializer
> kernel/trace/bpf_trace.c:312: warning: (near initialization for 'raw.frag.<anonymous>')
>
> Fixes: 555c8a8623a3a87 ("bpf: avoid stack copy and use skb ctx for event output")
> Acked-by: Daniel Borkmann <daniel@iogearbox.net>
> Cc: Alexei Starovoitov <ast@kernel.org>
> Cc: David S. Miller <davem@davemloft.net>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Applied.
prev parent reply other threads:[~2016-07-20 2:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 22:50 [patch 1/1] kernel/trace/bpf_trace.c: work around gcc-4.4.4 anon union initialization bug akpm
2016-07-19 0:33 ` Alexei Starovoitov
2016-07-19 0:38 ` Fengguang Wu
2016-07-19 2:38 ` Alexei Starovoitov
2016-07-19 3:07 ` Fengguang Wu
2016-07-19 8:19 ` Daniel Borkmann
2016-07-20 2:28 ` David Miller [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=20160719.192801.35741043299529276.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.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 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).