From: Vamsi Kodavanty <vamsi@araalinetworks.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: bpf <bpf@vger.kernel.org>, Andrii Nakryiko <andrii.nakryiko@gmail.com>
Subject: Re: [PATCH bpf v1] Add `core_btf_path` to `bpf_object_open_opts` to pass BTF path from skeleton program
Date: Mon, 11 Jan 2021 11:07:28 -0800 [thread overview]
Message-ID: <CADmGQ+3X7xtrYaKbUsd-0U=-phHvsVBtfMBbEgjvWf7WBzmfFg@mail.gmail.com> (raw)
In-Reply-To: <f5d58b88-cd96-4c78-ff22-4989c6b2ec96@iogearbox.net>
Thank you so much!. Will follow protocol and get back here.
Best Regards
Vamsi.
On Mon, Jan 11, 2021 at 6:14 AM Daniel Borkmann <daniel@iogearbox.net> wrote:
>
> On 1/9/21 3:36 AM, Vamsi Kodavanty wrote:
> [...]
> > Please do take a look. Also, I am not sure what the procedure is for submitting patches/reviews.
> > If anyone has any pointers to a webpage where this is described I can go through it. But, below are
> > the proposed changes.
>
> For submitting patches there is an official write-up here [0]. An example of a commit message
> can be found here [1]. Please make sure to add your own Signed-off-by before officially submitting
> the patch. If you are stuck somewhere please let us know so we can help.
>
> Cheers,
> Daniel
>
> [0] https://www.kernel.org/doc/html/latest/process/submitting-patches.html
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/patch/?id=e22d7f05e445165e58feddb4e40cc9c0f94453bc
next prev parent reply other threads:[~2021-01-11 19:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 2:36 [PATCH bpf v1] Add `core_btf_path` to `bpf_object_open_opts` to pass BTF path from skeleton program Vamsi Kodavanty
2021-01-11 14:13 ` Daniel Borkmann
2021-01-11 19:07 ` Vamsi Kodavanty [this message]
2021-01-11 22:02 ` Andrii Nakryiko
2021-01-12 3:33 ` Vamsi Kodavanty
2021-01-13 22:16 ` Vamsi Kodavanty
2021-01-14 3:21 ` Andrii Nakryiko
2021-01-14 3:52 ` Vamsi Kodavanty
2021-03-03 4:11 ` Andrii Nakryiko
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='CADmGQ+3X7xtrYaKbUsd-0U=-phHvsVBtfMBbEgjvWf7WBzmfFg@mail.gmail.com' \
--to=vamsi@araalinetworks.com \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
/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.