From: Randy Dunlap <randy.dunlap@oracle.com>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
Jens Axboe <jens.axboe@oracle.com>, Jan Kara <jack@suse.cz>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] writeback: Fix missing kernel-doc notation
Date: Fri, 11 Dec 2009 12:29:22 -0800 [thread overview]
Message-ID: <20091211122922.2b9e165c.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20091122123347.GA19022@localhost>
On Sun, 22 Nov 2009 20:33:47 +0800 Wu Fengguang wrote:
>
> Acked-by: Wu Fengguang <fengguang.wu@intel.com>
>
> Thanks!
applied, thanks.
> On Sun, Nov 22, 2009 at 04:16:09PM +0800, Jaswinder Singh Rajput wrote:
> >
> > Fix the following htmldocs warning:
> >
> > Warning(fs/fs-writeback.c:255): No description found for parameter 'sb'
> >
> > Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
> > Cc: Wu Fengguang <fengguang.wu@intel.com>
> > Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > Cc: Jan Kara <jack@suse.cz>
> > Cc: Jens Axboe <jens.axboe@oracle.com>
> > Cc: Randy Dunlap <randy.dunlap@oracle.com>
> > ---
> > fs/fs-writeback.c | 1 +
> > 1 files changed, 1 insertions(+), 0 deletions(-)
> >
> > diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
> > index 9d5360c..b15c97f 100644
> > --- a/fs/fs-writeback.c
> > +++ b/fs/fs-writeback.c
> > @@ -242,6 +242,7 @@ static void bdi_sync_writeback(struct backing_dev_info *bdi,
> > /**
> > * bdi_start_writeback - start writeback
> > * @bdi: the backing device to write from
> > + * @sb: write inodes from this super_block
> > * @nr_pages: the number of pages to write
> > *
> > * Description:
> > --
---
~Randy
prev parent reply other threads:[~2009-12-11 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-22 8:16 Jaswinder Singh Rajput
2009-11-22 12:33 ` Wu Fengguang
2009-12-11 20:29 ` Randy Dunlap [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=20091211122922.2b9e165c.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=a.p.zijlstra@chello.nl \
--cc=fengguang.wu@intel.com \
--cc=jack@suse.cz \
--cc=jaswinder@kernel.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®