From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Tobin C. Harding" <me@tobin.cc>
Cc: Jiri Slaby <jslaby@suse.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 3/3] tty_port: Fix kernel-docs warnings
Date: Wed, 19 Sep 2018 07:15:23 +0200 [thread overview]
Message-ID: <20180919051523.GC31598@kroah.com> (raw)
In-Reply-To: <20180918220246.GD22746@eros>
On Wed, Sep 19, 2018 at 08:02:46AM +1000, Tobin C. Harding wrote:
> On Tue, Sep 18, 2018 at 03:38:49PM +0200, Greg Kroah-Hartman wrote:
> > On Wed, Sep 12, 2018 at 05:50:44PM +1000, Tobin C. Harding wrote:
> > > Currently extracting the kernel-docs causes a six warnings of type
> > >
> > > warning: Function parameter or member 'foo' not described in 'bar'
> > >
> > > Add function parameter descriptions to the function kernel-docs.
> > >
> > > Signed-off-by: Tobin C. Harding <me@tobin.cc>
> > > ---
> > > drivers/tty/tty_port.c | 6 ++++++
> > > 1 file changed, 6 insertions(+)
> >
> > As I didn't take patch 2/3, this one doesn't apply :(
>
> Oh I thought this whole set would have been ignored because of comments
> on it.
Not at all, kerneldoc cleanups are great to have!
> I've been working on doing these changes for all of drivers/tty/
That's good, it needs it, thanks.
greg k-h
prev parent reply other threads:[~2018-09-19 5:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 7:50 [PATCH 0/3] ttp_port: Clean up kernel-docs Tobin C. Harding
2018-09-12 7:50 ` [PATCH 1/3] tty_port: Remove incorrect whitespace after comments Tobin C. Harding
2018-09-12 7:50 ` [PATCH 2/3] tty_port: Fix function name and brief desc Tobin C. Harding
2018-09-12 9:31 ` Johan Hovold
2018-09-12 21:08 ` Tobin C. Harding
2018-09-18 13:37 ` Greg Kroah-Hartman
2018-09-12 7:50 ` [PATCH 3/3] tty_port: Fix kernel-docs warnings Tobin C. Harding
2018-09-18 13:38 ` Greg Kroah-Hartman
2018-09-18 22:02 ` Tobin C. Harding
2018-09-19 5:15 ` Greg Kroah-Hartman [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=20180919051523.GC31598@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@tobin.cc \
/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).