From: Yonghong Song <yonghong.song@linux.dev>
To: Sergey Kacheev <s.kacheev@gmail.com>,
bpf@vger.kernel.org, Alan Maguire <alan.maguire@oracle.com>
Subject: Re: [PATCH v3 bpf-next] libbpf: Use local includes inside the library
Date: Wed, 2 Aug 2023 12:06:39 -0700 [thread overview]
Message-ID: <87ff8db2-a5d0-ccd0-0808-c83c4c135e05@linux.dev> (raw)
In-Reply-To: <CAJVhQqUg6OKq6CpVJP5ng04Dg+z=igevPpmuxTqhsR3dKvd9+Q@mail.gmail.com>
On 8/2/23 11:22 AM, Sergey Kacheev wrote:
> In our monrepo, we try to minimize special processing when importing
> (aka vendor) third-party source code. Ideally, we try to import
> directly from the repositories with the code without changing it, we
> try to stick to the source code dependency instead of the artifact
> dependency. In the current situation, a patch has to be made for
> libbpf to fix the includes in bpf headers so that they work directly
> from libbpf/src.
>
> Signed-off-by: Sergey Kacheev <s.kacheev@gmail.com>
Acked-by: Yonghong Song <yonghong.song@linux.dev>
next prev parent reply other threads:[~2023-08-02 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 18:22 [PATCH v3 bpf-next] libbpf: Use local includes inside the library Sergey Kacheev
2023-08-02 19:06 ` Yonghong Song [this message]
2023-08-04 22:20 ` patchwork-bot+netdevbpf
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=87ff8db2-a5d0-ccd0-0808-c83c4c135e05@linux.dev \
--to=yonghong.song@linux.dev \
--cc=alan.maguire@oracle.com \
--cc=bpf@vger.kernel.org \
--cc=s.kacheev@gmail.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