All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Dave Tucker <dave@dtucker.co.uk>, bpf@vger.kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	kafai@fb.com, songliubraving@fb.com, john.fastabend@gmail.com,
	kpsingh@kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH bpf-next 2/2] bpf, docs: document BPF_MAP_TYPE_ARRAY
Date: Mon, 22 Nov 2021 13:33:10 -0700	[thread overview]
Message-ID: <871r38vsl5.fsf@meer.lwn.net> (raw)
In-Reply-To: <d1ab737c-5e00-4781-90d4-495400d90b0f@www.fastmail.com>

"Dave Tucker" <dave@dtucker.co.uk> writes:

> On Mon, 22 Nov 2021, at 19:15, Jonathan Corbet wrote:
>> Dave Tucker <dave@dtucker.co.uk> writes:
>>
>> When you add a new BPF file, you need to add it to the corresponding
>> index.rst file as well.  Otherwise it won't be part of the docs build
>> and will, instead, generate the warning you surely saw when you tested
>> the build...:)
>
> I did test the build and I don't think I introduced any new warnings :)
>
> This file is included in the docs build via the glob pattern that I added to 
> the toctree in Documentation/bpf/maps.rst, which was recently applied to
> bpf-next [1].

Interesting, I didn't know about :glob: - thanks for teaching me
something and apologies for the noise :)

Thanks,

jon

  reply	other threads:[~2021-11-22 20:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22 17:19 [PATCH bpf-next 0/2] bpf, docs: Document BPF_MAP_TYPE_ARRAY Dave Tucker
2021-11-22 17:19 ` [PATCH bpf-next 1/2] bpf, docs: add kernel version to map_cgroup_storage Dave Tucker
2021-11-22 17:19 ` [PATCH bpf-next 2/2] bpf, docs: document BPF_MAP_TYPE_ARRAY Dave Tucker
2021-11-22 19:15   ` Jonathan Corbet
2021-11-22 19:33     ` Dave Tucker
2021-11-22 20:33       ` Jonathan Corbet [this message]
2021-11-23  3:53   ` 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=871r38vsl5.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=dave@dtucker.co.uk \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=songliubraving@fb.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.