From: Fengguang Wu <fengguang.wu@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] regulator: fix fatal kernel-doc error
Date: Thu, 19 Sep 2013 23:26:26 +0800 [thread overview]
Message-ID: <20130919152626.GB7925@localhost> (raw)
In-Reply-To: <20130919140131.GB21013@sirena.org.uk>
On Thu, Sep 19, 2013 at 03:01:31PM +0100, Mark Brown wrote:
> On Wed, Sep 18, 2013 at 07:33:28AM +0800, Fengguang Wu wrote:
> > On Tue, Sep 17, 2013 at 08:23:55PM +0100, Mark Brown wrote:
>
> > > Could these checks be added to Fengguang's tester? If nobody's looking
> > > at the output (I've never found the processed output useful myself) or
> > > running the tool then it's a bit worrying...
>
> > Yes, I'm running "make htmldocs" checks and send out all new warnings:
>
> > Does that sound enough?
>
> I'd expect it to be but then it seems like the issue that Randy found
> wasn't picked up... not sure if there's some other build that would
> cover it or something.
Yes.. it was missed because the script used to only grep for
"Warning(.*)" patterns and ignored the "Error(.*)" ones. Fixed
since last email.
Thanks,
Fengguang
next prev parent reply other threads:[~2013-09-19 15:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 1:08 [PATCH] regulator: fix fatal kernel-doc error Randy Dunlap
2013-09-17 10:32 ` Mark Brown
2013-09-17 17:09 ` Randy Dunlap
2013-09-17 19:23 ` Mark Brown
2013-09-17 23:33 ` Fengguang Wu
2013-09-19 14:01 ` Mark Brown
2013-09-19 15:26 ` Fengguang Wu [this message]
2013-09-19 15:52 ` Mark Brown
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=20130919152626.GB7925@localhost \
--to=fengguang.wu@intel.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=torvalds@linux-foundation.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