linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: "imagedong(董梦龙)" <imagedong@tencent.com>, linux-doc@vger.kernel.org
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>,
	David Miller <davem@davemloft.net>,
	Networking <netdev@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>
Subject: Re: [Internet]linux-next: build warning after merge of the net-next tree
Date: Thu, 25 Aug 2022 10:42:08 -0700	[thread overview]
Message-ID: <20220825104208.592a2df2@kernel.org> (raw)
In-Reply-To: <07263247-4906-4A72-A1A2-CAB41F115EB7@tencent.com>

On Thu, 25 Aug 2022 07:55:36 +0000 imagedong(董梦龙) wrote:
> > After merging the net-next tree, today's linux-next build (htmldocs)
> > produced this warning:
> > 
> > Documentation/networking/kapi:26: net/core/skbuff.c:780: WARNING: Error in declarator or parameters
> > Invalid C declaration: Expecting "(" in parameters. [error at 19]
> >   void __fix_address kfree_skb_reason (struct sk_buff *skb, enum skb_drop_reason reason)
> >   -------------------^
> > 
> > Introduced by commit
> > 
> >   c205cc7534a9 ("net: skb: prevent the split of kfree_skb_reason() by gcc")
> >   
> 
> Yeah, I commited this patch. May I ask what command did you use to
> produce this warning? I tried the following command, but not success:
> 
>   make V=2 SPHINXDIRS="networking" htmldocs
> 
> Hmm.......what does this warning means? Does it don't like this
> function attribute?

It popped up for me on a clean build of

	make htmldocs

There's a lot of other warnings but you should see this one, too.

I think you need to add the new keyword to one of the tables in
Documentation/conf.py

      reply	other threads:[~2022-08-25 17:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25  5:41 linux-next: build warning after merge of the net-next tree Stephen Rothwell
2022-08-25  7:55 ` [Internet]linux-next: " imagedong(董梦龙)
2022-08-25 17:42   ` Jakub Kicinski [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=20220825104208.592a2df2@kernel.org \
    --to=kuba@kernel.org \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=imagedong@tencent.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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).