public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Tim Bird <tim.bird@sonymobile.com>, Jonathan Corbet <corbet@lwn.net>
Cc: "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"tbird20d@gmail.com" <tbird20d@gmail.com>
Subject: Re: [PATCH] doc: Add more workqueue functions to the documentation
Date: Fri, 14 Aug 2015 16:41:15 -0700	[thread overview]
Message-ID: <55CE7C9B.5060405@infradead.org> (raw)
In-Reply-To: <55CE6FDC.3010700@sonymobile.com>

On 08/14/15 15:46, Tim Bird wrote:
> 
> 
> On 08/13/2015 04:45 PM, Jonathan Corbet wrote:
>> On Mon, 10 Aug 2015 15:16:16 -0700
>> Tim Bird <tim.bird@sonymobile.com> wrote:
>>
>>> There are some workqueue functions declared in workqueue.h, so include
>>> that in the workqueue section of the DocBook docs.
>>
>> Applied to the docs tree, thanks.
>>
>> It sure would be nice if changes like this were accompanied by a patch
>> fixing the additional warnings it drags in ... :)  In this case I've put
>> something together for workqueue.h and will send it off shortly.
> 
> My apologies.  
> 
> When I do 'make mandocs', the only messages from workqueue.h that I noticed
> were like the following:
> 
> Warn: meta author : no refentry/info/author                        queue_delayed_work
> Note: meta author : see http://docbook.sf.net/el/author            queue_delayed_work
> Warn: meta author : no author data, so inserted a fixme            queue_delayed_work
> Note: Writing queue_delayed_work.9
> 
> But there are over 4000 of these messages when I make mandocs, so I assumed
> ignoring them was OK.
> 
> Are these what you saw or was it something else?

These are the new warnings that I saw:

Warning(..//include/linux/workqueue.h:271): No description found for parameter 'w'
Warning(..//include/linux/workqueue.h:271): Excess function parameter 'work' description in 'delayed_work_pending'
Warning(..//include/linux/workqueue.h:390): Excess function parameter 'args' description in 'alloc_workqueue'
Warning(..//include/linux/workqueue.h:411): Excess function parameter 'args' description in 'alloc_ordered_workqueue'

and Jon has already posted a patch for these.

> Do you know how to get rid of these messages?  
> 
> It's a bit of a pain rebuilding.  When I make a change, it rebuilds everything.
> My build of mandocs takes 27 minutes and generates over 9000 messages.
> Somewhere in the middle of that must have been some other messages related to
> workqueue.h that I missed.
> 
> However, I'll try to fix build errors in the future.


-- 
~Randy

  reply	other threads:[~2015-08-14 23:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10 22:16 [PATCH] doc: Add more workqueue functions to the documentation Tim Bird
2015-08-11 22:52 ` Randy Dunlap
2015-08-13 23:45 ` Jonathan Corbet
2015-08-14 22:46   ` Tim Bird
2015-08-14 23:41     ` Randy Dunlap [this message]
2015-08-15 13:27     ` Jonathan Corbet
2015-08-24 15:32       ` Tim Bird

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=55CE7C9B.5060405@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tbird20d@gmail.com \
    --cc=tim.bird@sonymobile.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox