public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>
Subject: Re: rcu kernel-doc issues (4.14-rc1)
Date: Mon, 16 Oct 2017 13:07:49 -0700	[thread overview]
Message-ID: <20171016200749.GF3521@linux.vnet.ibm.com> (raw)
In-Reply-To: <db72de9a-3d8b-6dbc-0e6f-3481f1dd9754@infradead.org>

On Mon, Oct 16, 2017 at 12:58:28PM -0700, Randy Dunlap wrote:
> Hi Jonathan and Paul,
> 
> Please include these fixes before 4.14 final.

Hello, Randy,

I currently have them queued up for the 4.15 merge window.  Will that
work for you?

							Thanx, Paul

> Thanks.
> 
> On 09/17/17 12:49, Paul E. McKenney wrote:
> > On Sun, Sep 17, 2017 at 10:57:42AM -0700, Randy Dunlap wrote:
> >> On 09/17/17 10:47, Paul E. McKenney wrote:
> >>> On Sat, Sep 16, 2017 at 09:41:45PM -0700, Paul E. McKenney wrote:
> >>>> On Sat, Sep 16, 2017 at 06:26:04PM -0700, Randy Dunlap wrote:
> >>>>> On 4.14-rc1, I am seeing lots of warnings on rcu kernel-doc:
> >>>>>
> >>>>> .. kernel-doc:: include/linux/rcupdate.h
> >>>>>    :external:
> >>>>> ./Documentation/core-api/kernel-api.rst:357: ERROR: Error in "kernel-doc" directive:
> >>>>> unknown option: "external".
> >>>>
> >>>> $ grep external include/linux/rcupdate.h
> >>>>  * by a single external-to-structure RCU-protected pointer, then you may
> >>>>  * external-to-structure pointer -after- you have completely initialized
> >>>>
> >>>> Do these comments somehow qualify as an "external" option?  If so, how
> >>>> do I tell kernel-doc to ignore them?  Or must I reword them to avoid
> >>>> the word "external"?
> >>>>
> >>>>> .. kernel-doc:: include/linux/rcupdate_wait.h
> >>>>>    :external:
> >>>>> ./Documentation/core-api/kernel-api.rst:360: ERROR: Error in "kernel-doc" directive:
> >>>>> unknown option: "external".
> >>>>
> >>>> $ grep external include/linux/rcupdate_wait.h
> >>>>
> >>>> There is no occurrence of the string "external" in this file.  So this
> >>>> "external" option is unknown to me as well.  So, any hints on how I
> >>>> should interpret these error messages?
> >>>
> >>> And thanks to Akira Yokosawa for pointing out my confusion in reading
> >>> these error messages.  The line numbers of course apply to the file
> >>> Documentation/core-api/kernel-api.rst rather than the various RCU
> >>> C-language source files.
> >>>
> >>> The patch below removes the error messages for me.  Is this what you
> >>> had in mind?  (Might need other options at some point, but somewhere
> >>> to start.)
> >>>
> >>
> >> Yes, much better.  Thanks.
> >>
> >> Just some missing kernel-doc on parameters mostly remaining:
> > 
> > I have now fixed a number of these, thank you.
> > 
> > Any hints for how to represent code samples within a "/**" comment?
> > 
> > /home/git/linux-2.6-tip/include/linux/rcupdate.h:559: ERROR: Unexpected indentation.
> > /home/git/linux-2.6-tip/include/linux/rcupdate.h:563: WARNING: Block quote ends without a blank line; unexpected unindent.
> > /home/git/linux-2.6-tip/include/linux/rcupdate.h:777: ERROR: Unexpected indentation.
> > /home/git/linux-2.6-tip/include/linux/rcupdate.h:778: WARNING: Block quote ends without a blank line; unexpected unindent.
> > 
> > 							Thanx, Paul
> > 
> >> ../include/linux/rcupdate.h:818: warning: No description found for parameter 'p'
> >> ../include/linux/rcupdate.h:818: warning: No description found for parameter 'v'
> >> ../include/linux/rcupdate.h:826: warning: No description found for parameter 'p'
> >> ../include/linux/rcupdate.h:826: warning: No description found for parameter 'v'
> >> ../include/linux/srcu.h:95: warning: No description found for parameter 'sp'
> >> ../kernel/rcu/srcutree.c:873: warning: No description found for parameter 'rhp'
> >> ../kernel/rcu/srcutree.c:873: warning: Excess function parameter 'head' description in 'call_srcu'
> >> ../include/linux/rculist.h:302: warning: Incorrect use of kernel-doc format:  * list_first_or_null_rcu - get the first element from a list
> >> ../include/linux/rculist.h:317: warning: No description found for parameter 'ptr'
> >> ../include/linux/rculist.h:317: warning: No description found for parameter 'type'
> >> ../include/linux/rculist.h:317: warning: No description found for parameter 'member'
> >> ../kernel/rcu/sync.c:94: warning: No description found for parameter 'rsp'
> >> ../kernel/rcu/sync.c:162: warning: No description found for parameter 'rcu'
> >> ../kernel/rcu/sync.c:162: warning: Excess function parameter 'rsp' description in 'rcu_sync_func'
> >>
> >>>
> >>> ------------------------------------------------------------------------
> >>>
> >>> diff --git a/Documentation/core-api/kernel-api.rst b/Documentation/core-api/kernel-api.rst
> >>> index 8282099e0cbf..30b2666bf494 100644
> >>> --- a/Documentation/core-api/kernel-api.rst
> >>> +++ b/Documentation/core-api/kernel-api.rst
> >>> @@ -352,44 +352,44 @@ Read-Copy Update (RCU)
> >>>  ----------------------
> >>>  
> >>>  .. kernel-doc:: include/linux/rcupdate.h
> >>> -   :external:
> >>> +   :export
> >>>  
> >>>  .. kernel-doc:: include/linux/rcupdate_wait.h
> >>> -   :external:
> >>> +   :export
> >>>  
> >>>  .. kernel-doc:: include/linux/rcutree.h
> >>> -   :external:
> >>> +   :export
> >>>  
> >>>  .. kernel-doc:: kernel/rcu/tree.c
> >>> -   :external:
> >>> +   :export
> >>>  
> >>>  .. kernel-doc:: kernel/rcu/tree_plugin.h
> >>> -   :external:
> >>> +   :export
> >>>  
> >>>  .. kernel-doc:: kernel/rcu/tree_exp.h
> >>> -   :external:
> >>> +   :export
> >>>  
> >>>  .. kernel-doc:: kernel/rcu/update.c
> >>> -   :external:
> >>> +   :export
> >>>  
> >>>  .. kernel-doc:: include/linux/srcu.h
> >>> -   :external:
> >>> +   :export
> >>>  
> >>>  .. kernel-doc:: kernel/rcu/srcutree.c
> >>> -   :external:
> >>> +   :export
> >>>  
> >>>  .. kernel-doc:: include/linux/rculist_bl.h
> >>> -   :external:
> >>> +   :export
> >>>  
> >>>  .. kernel-doc:: include/linux/rculist.h
> >>> -   :external:
> >>> +   :export
> >>>  
> >>>  .. kernel-doc:: include/linux/rculist_nulls.h
> >>> -   :external:
> >>> +   :export
> >>>  
> >>>  .. kernel-doc:: include/linux/rcu_sync.h
> >>> -   :external:
> >>> +   :export
> >>>  
> >>>  .. kernel-doc:: kernel/rcu/sync.c
> >>> -   :external:
> >>> +   :export
> 
> 
> -- 
> ~Randy
> 

  reply	other threads:[~2017-10-16 20:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-17  1:26 rcu kernel-doc issues (4.14-rc1) Randy Dunlap
2017-09-17  4:41 ` Paul E. McKenney
2017-09-17 17:47   ` Paul E. McKenney
2017-09-17 17:57     ` Randy Dunlap
2017-09-17 19:49       ` Paul E. McKenney
2017-09-18  2:40         ` Paul E. McKenney
2017-09-18  7:30           ` Markus Heiser
2017-09-18 14:21             ` Paul E. McKenney
2017-10-16 19:58         ` Randy Dunlap
2017-10-16 20:07           ` Paul E. McKenney [this message]
2017-10-16 20:18             ` Randy Dunlap
2017-10-16 20:26               ` Paul E. McKenney
2017-10-16 21:46                 ` Randy Dunlap
2017-10-16 23:35                   ` Paul E. McKenney
2017-10-18 16:03                 ` Jonathan Corbet
2017-10-18 16:27                   ` Paul E. McKenney
2017-10-18 16:36                     ` Jonathan Corbet
2017-10-20 16:42                       ` Paul E. McKenney
2017-10-20 16:53                         ` Randy Dunlap
2017-09-18  6:43 ` Markus Heiser

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=20171016200749.GF3521@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    /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