linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Marcos Paulo de Souza <marcos.mage@gmail.com>
Cc: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/2] fs/fs-writeback.c: Fix issue on make htmldocs
Date: Wed, 09 Nov 2011 18:03:44 -0800	[thread overview]
Message-ID: <4EBB3100.1050805@xenotime.net> (raw)
In-Reply-To: <1320871694-3582-1-git-send-email-marcos.mage@gmail.com>

On 11/09/2011 12:48 PM, Marcos Paulo de Souza wrote:
> Fixed some documentation of functions used by the make htmldocs.
> 
> Signed-off-by: Marcos Paulo de Souza <marcos.mage@gmail.com>

Acked-by: Randy Dunlap <rdunlap@xenotime.net>

Thanks.

> ---
>  fs/fs-writeback.c |    5 +++++
>  1 files changed, 5 insertions(+), 0 deletions(-)
> 
> diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
> index 73c3992..ac86f8b 100644
> --- a/fs/fs-writeback.c
> +++ b/fs/fs-writeback.c
> @@ -156,6 +156,7 @@ __bdi_start_writeback(struct backing_dev_info *bdi, long nr_pages,
>   * bdi_start_writeback - start writeback
>   * @bdi: the backing device to write from
>   * @nr_pages: the number of pages to write
> + * @reason: reason why some writeback work was initiated
>   *
>   * Description:
>   *   This does WB_SYNC_NONE opportunistic writeback. The IO is only
> @@ -1223,6 +1224,7 @@ static void wait_sb_inodes(struct super_block *sb)
>   * writeback_inodes_sb_nr -	writeback dirty inodes from given super_block
>   * @sb: the superblock
>   * @nr: the number of pages to write
> + * @reason: reason why some writeback work initiated
>   *
>   * Start writeback on some inodes on this super_block. No guarantees are made
>   * on how many (if any) will be written, and this function does not wait
> @@ -1251,6 +1253,7 @@ EXPORT_SYMBOL(writeback_inodes_sb_nr);
>  /**
>   * writeback_inodes_sb	-	writeback dirty inodes from given super_block
>   * @sb: the superblock
> + * @reason: reason why some writeback work was initiated
>   *
>   * Start writeback on some inodes on this super_block. No guarantees are made
>   * on how many (if any) will be written, and this function does not wait
> @@ -1265,6 +1268,7 @@ EXPORT_SYMBOL(writeback_inodes_sb);
>  /**
>   * writeback_inodes_sb_if_idle	-	start writeback if none underway
>   * @sb: the superblock
> + * @reason: reason why some writeback work was initiated
>   *
>   * Invoke writeback_inodes_sb if no writeback is currently underway.
>   * Returns 1 if writeback was started, 0 if not.
> @@ -1285,6 +1289,7 @@ EXPORT_SYMBOL(writeback_inodes_sb_if_idle);
>   * writeback_inodes_sb_if_idle	-	start writeback if none underway
>   * @sb: the superblock
>   * @nr: the number of pages to write
> + * @reason: reason why some writeback work was initiated
>   *
>   * Invoke writeback_inodes_sb if no writeback is currently underway.
>   * Returns 1 if writeback was started, 0 if not.


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2011-11-10  2:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09 20:48 [PATCH 2/2] fs/fs-writeback.c: Fix issue on make htmldocs Marcos Paulo de Souza
2011-11-10  2:03 ` Randy Dunlap [this message]
2011-11-17  0:24 ` Marcos Paulo de Souza

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=4EBB3100.1050805@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=marcos.mage@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    /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).