From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Jakub Kicinski <jakub.kicinski@netronome.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Thomas Richter <tmricht@linux.ibm.com>,
Hendrik Brueckner <brueckner@linux.ibm.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [RFC/fix] Re: libbpf build broken on musl libc (Alpine Linux)
Date: Tue, 18 Sep 2018 10:15:17 -0300 [thread overview]
Message-ID: <20180918131517.GA32227@kernel.org> (raw)
In-Reply-To: <20180918005256.7uutwda4s3ofoxpd@ast-mbp>
Em Mon, Sep 17, 2018 at 05:52:59PM -0700, Alexei Starovoitov escreveu:
> > +++ b/tools/lib/bpf/str_error.h
> > @@ -0,0 +1,6 @@
> > +// SPDX-License-Identifier: GPL-2.1
>
> LGPL-2.1 in the above?
Sure, will fix.
> The rest looks good to me.
Will that that as an Acked-by: you, ok?
> Should we take it via bpf-next tree?
No need, I have it already in perf/urgent, will push shortly to Ingo.
Thanks,
- Arnaldo
> If you feel there is an urgency to fix musl build, we can take it via bpf tree too.
>
> Jakub, thoughts? you've been messing with strerror last..
next prev parent reply other threads:[~2018-09-18 13:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 17:29 libbpf build broken on musl libc (Alpine Linux) Arnaldo Carvalho de Melo
2018-09-11 10:22 ` Jakub Kicinski
2018-09-11 12:15 ` Arnaldo Carvalho de Melo
2018-09-11 21:24 ` Alexei Starovoitov
2018-09-13 18:32 ` [RFC/fix] " Arnaldo Carvalho de Melo
2018-09-13 18:56 ` Alexei Starovoitov
2018-09-13 19:44 ` Arnaldo Carvalho de Melo
2018-09-17 15:16 ` Arnaldo Carvalho de Melo
2018-09-18 0:52 ` Alexei Starovoitov
2018-09-18 2:39 ` Jakub Kicinski
2018-09-18 4:18 ` Alexei Starovoitov
2018-09-18 13:15 ` Arnaldo Carvalho de Melo [this message]
2018-09-19 11:36 ` [tip:perf/urgent] tools lib bpf: Provide wrapper for strerror_r to build in !_GNU_SOURCE systems tip-bot for Arnaldo Carvalho de Melo
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=20180918131517.GA32227@kernel.org \
--to=acme@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=arnaldo.melo@gmail.com \
--cc=brueckner@linux.ibm.com \
--cc=daniel@iogearbox.net \
--cc=jakub.kicinski@netronome.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tmricht@linux.ibm.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 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.