linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: andrii@kernel.org, davem@davemloft.net,
	linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
	lorenzo@kernel.org, mtahhan@redhat.com, netdev@vger.kernel.org,
	Akira Yokosawa <akiyks@gmail.com>
Subject: Re: linux-next: build warnings after merge of the net-next tree
Date: Mon, 14 Nov 2022 17:00:45 +0900	[thread overview]
Message-ID: <6a7f6bb3-bbd4-9b71-b069-b543de067079@gmail.com> (raw)
In-Reply-To: <20221114183131.3c68e1b5@canb.auug.org.au>

On Mon, 14 Nov 2022 18:31:31 +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the net-next tree, today's linux-next build (htmldocs)
> produced these warnings:
> 
> Documentation/bpf/map_cpumap.rst:50: WARNING: Error in declarator or parameters
> Invalid C declaration: Expected identifier in nested name. [error at 67]
>   int bpf_map_update_elem(int fd, const void *key, const void *value,
>   -------------------------------------------------------------------^
> Documentation/bpf/map_cpumap.rst:50: WARNING: Error in declarator or parameters
> Invalid C declaration: Expecting "(" in parameters. [error at 11]
>   __u64 flags);
>   -----------^
> Documentation/bpf/map_cpumap.rst:73: WARNING: Duplicate C declaration, also defined at bpf/map_array:35.
> Declaration is '.. c:function:: int bpf_map_lookup_elem(int fd, const void *key, void *value);'.
> 
> Introduced by commit
> 
>   161939abc80b ("docs/bpf: Document BPF_MAP_TYPE_CPUMAP map")

Hi Stephen,

Maryam has posted a patch at:

    https://lore.kernel.org/r/20221113103327.3287482-1-mtahhan@redhat.com/

        Thanks, Akira

> 
> -- 
> Cheers,
> Stephen Rothwell

  reply	other threads:[~2022-11-14  8:00 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14  7:31 linux-next: build warnings after merge of the net-next tree Stephen Rothwell
2022-11-14  8:00 ` Akira Yokosawa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-04  4:47 Stephen Rothwell
2023-09-18  3:15 Stephen Rothwell
2023-09-18  7:43 ` Bagas Sanjaya
2023-06-26  6:29 Stephen Rothwell
2023-09-05 22:55 ` Stephen Rothwell
2023-09-05 23:44   ` Jakub Kicinski
2023-06-13  6:31 Stephen Rothwell
2023-06-20 16:15 ` Jakub Kicinski
2023-06-20 23:12   ` Saeed Mahameed
2021-06-15 11:23 Stephen Rothwell
2021-06-15 11:12 Stephen Rothwell
2021-03-18  6:22 Stephen Rothwell
2021-02-18 20:52 Stephen Rothwell
2021-02-19  8:44 ` Stephen Rothwell
2021-02-19 14:57   ` Kalle Valo
2020-12-14  9:10 Stephen Rothwell
2020-12-21  1:28 ` Stephen Rothwell
2021-01-05  6:19   ` Stephen Rothwell
2019-11-05  1:45 Stephen Rothwell
2017-03-20  6:07 Stephen Rothwell
2017-01-18  0:37 Stephen Rothwell
2016-11-22  1:22 Stephen Rothwell
2016-11-22  1:28 ` Florian Fainelli
2016-11-22  8:23   ` Thomas Petazzoni
2015-06-20 13:12 Stephen Rothwell
2015-06-20 17:40 ` Florian Westphal
2015-06-20 18:31   ` Pablo Neira Ayuso
2015-05-14  7:12 Stephen Rothwell
2015-05-14 14:47 ` Willem de Bruijn

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=6a7f6bb3-bbd4-9b71-b069-b543de067079@gmail.com \
    --to=akiyks@gmail.com \
    --cc=andrii@kernel.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lorenzo@kernel.org \
    --cc=mtahhan@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).