mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: Fabian Frederick <fabf@skynet.be>
Cc: linux-kernel@vger.kernel.org,
	Steven Whitehouse <swhiteho@redhat.com>,
	cluster-devel@redhat.com
Subject: Re: [PATCH 1/1 linux-next] gfs2: kerneldoc warning fixes
Date: Tue, 5 May 2015 14:46:40 -0400 (EDT)	[thread overview]
Message-ID: <1916274112.12335830.1430851600357.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1430591474-23108-1-git-send-email-fabf@skynet.be>

----- Original Message -----
> Fixes the following kernel-doc warnings:
> Warning(fs/gfs2/aops.c:180): No description found for parameter 'wbc'
> Warning(fs/gfs2/aops.c:236): No description found for parameter 'end'
> Warning(fs/gfs2/aops.c:236): No description found for parameter 'done_index'
> Warning(fs/gfs2/aops.c:236): Excess function parameter 'writepage'
> description in 'gfs2_write_jdata_pagevec'
> Warning(fs/gfs2/aops.c:346): Excess function parameter 'writepage'
> description in 'gfs2_write_cache_jdata'
> Warning(fs/gfs2/aops.c:346): Excess function parameter 'data' description in
> 'gfs2_write_cache_jdata'
> Warning(fs/gfs2/aops.c:605): No description found for parameter 'file'
> Warning(fs/gfs2/aops.c:605): No description found for parameter 'mapping'
> Warning(fs/gfs2/aops.c:605): No description found for parameter 'pages'
> Warning(fs/gfs2/aops.c:605): No description found for parameter 'nr_pages'
> Warning(fs/gfs2/aops.c:870): No description found for parameter 'copied'
> 
> Signed-off-by: Fabian Frederick <fabf@skynet.be>

Hi,

Thanks. Now in the for-next branch of the linux-gfs2 tree:
https://git.kernel.org/cgit/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs/gfs2?h=for-next&id=1272574bf94874a644ea82fad321034c15b157ac

Regards,

Bob Peterson
Red Hat File Systems

      reply	other threads:[~2015-05-05 18:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-02 18:31 Fabian Frederick
2015-05-05 18:46 ` Bob Peterson [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=1916274112.12335830.1430851600357.JavaMail.zimbra@redhat.com \
    --to=rpeterso@redhat.com \
    --cc=cluster-devel@redhat.com \
    --cc=fabf@skynet.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swhiteho@redhat.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
Powered by JetHome