mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: David Vernet <void@manifault.com>
Cc: Sreevani Sreejith <ssreevani@meta.com>,
	bpf@vger.kernel.org, psreep@gmail.com, andrii@kernel.org,
	mykolal@meta.com, Linux-kernel@vger.kernel.org,
	bagasdotme@gmail.com
Subject: Re: [PATCH V4 bpf-next] BPF, docs: libbpf Overview Document
Date: Fri, 17 Mar 2023 16:19:52 -0700	[thread overview]
Message-ID: <CAEf4BzaZ95Gv3Dkke+1gv1nRG41sroMaFb8Lqv93G7LAL7XBCA@mail.gmail.com> (raw)
In-Reply-To: <20230317225259.GA28462@maniforge>

On Fri, Mar 17, 2023 at 3:53 PM David Vernet <void@manifault.com> wrote:
>
> On Wed, Mar 15, 2023 at 12:54:05PM -0700, Sreevani Sreejith wrote:
> > From: Sreevani <ssreevani@meta.com>
> >
> > This patch documents overview of libbpf, including its features for
> > developing BPF programs.
> >
> > Signed-off-by: Sreevani <ssreevani@meta.com>
>
> Looks great, thanks Sreevani.
>
> Acked-by: David Vernet <void@manifault.com>
>

Applied suggestions and switched to consistent "=====" over/under top
level header in both files. Applied to bpf-next, thanks!

> > ---
> > Changelog:
> >
> > v3 = https://lore.kernel.org/all/20230310180928.2462527-1-ssreevani@meta.com/
> > v3 -> v4:
> >    * Update BTF types link
> >    * Update patch summary
> >    * Indent code options line
> >    * Update "See also" wording
> >
> >  Documentation/bpf/libbpf/index.rst           |  27 ++-
> >  Documentation/bpf/libbpf/libbpf_overview.rst | 228 +++++++++++++++++++
> >  2 files changed, 246 insertions(+), 9 deletions(-)
> >  create mode 100644 Documentation/bpf/libbpf/libbpf_overview.rst
> >
> > diff --git a/Documentation/bpf/libbpf/index.rst b/Documentation/bpf/libbpf/index.rst
> > index f9b3b252e28f..3ac8c06fb8f4 100644
> > --- a/Documentation/bpf/libbpf/index.rst
> > +++ b/Documentation/bpf/libbpf/index.rst
> > @@ -2,23 +2,32 @@
> >
> >  .. _libbpf:
> >
> > +######
> >  libbpf
> > -======
> > +######
> > +
> > +If you are looking to develop BPF applications using the libbpf library, this
> > +directory contains important documentation that you should read.
> > +
> > +To get started, it is recommended to begin with the :doc:`libbpf Overview
> > +<libbpf_overview>` document, which provides a high-level understanding of the
> > +libbpf APIs and their usage. This will give you a solid foundation to start
> > +exploring and utilizing the various features of libbpf to develop your BPF
> > +applications.
> >
> >  .. toctree::
> >     :maxdepth: 1
> >
> > +   libbpf_overview
> >     API Documentation <https://libbpf.readthedocs.io/en/latest/api.html>
> >     program_types
> >     libbpf_naming_convention
> >     libbpf_build
> >

[...]

      reply	other threads:[~2023-03-17 23:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 19:54 Sreevani Sreejith
2023-03-17 22:52 ` David Vernet
2023-03-17 23:19   ` Andrii Nakryiko [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=CAEf4BzaZ95Gv3Dkke+1gv1nRG41sroMaFb8Lqv93G7LAL7XBCA@mail.gmail.com \
    --to=andrii.nakryiko@gmail.com \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=andrii@kernel.org \
    --cc=bagasdotme@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=mykolal@meta.com \
    --cc=psreep@gmail.com \
    --cc=ssreevani@meta.com \
    --cc=void@manifault.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

all inboxes | Powered by JetHome®