Re: [PATCH bpf-next 0/3] Autogenerating API documentation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jun 1, 2021 at 3:01 PM Jonathan Corbet <corbet@xxxxxxx> wrote:
>
> Grant Seltzer Richman <grantseltzer@xxxxxxxxx> writes:
>
> > Jonathan - am I missing something about how we can version libbpf
> > separately from the actual kernel docs?
>
> Sorry, I missed this before.  I guess I still don't understand the
> question, though; could you explain what the problem is here?  Apologies
> for being so slow...

No worries, thanks for your response and feedback! I made it confusing
by not including v2 in my second patch series (this is v1)

Andrii cuts releases of libbpf using the github mirror at
github.com/libbpf/libbpf. There's more context in the README there,
but most of the major distributions package libbpf from this mirror.
Since developers that use libbpf in their applications include libbpf
based on these github releases instead of versions of Linux (i.e. I
use libbpf 0.4, not libbpf from linux 5.14), it's important to have
the API documentation be labeled by the github release versions. Is
there any mechanism in the kernel docs that would allow us to do that?
Would it make more sense for the libbpf community to maintain their
own documentation system/website for this purpose?

>
> Thanks,
>
> jon



[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux