All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li RongQing <lirongqing@baidu.com>
To: linux-fsdevel@vger.kernel.org
Cc: viro@zeniv.linux.org.uk
Subject: [PATCH] fs: remove obsolete comment
Date: Fri, 29 Jun 2018 16:31:19 +0800	[thread overview]
Message-ID: <1530261079-25068-1-git-send-email-lirongqing@baidu.com> (raw)

After e8e8a0c6c9b [writeback: move nr_pages == 0 logic to one
location], the nr_page argument of __wakeup_flusher_threads_bdi
has been removed, so remove this obsolete comment

After bc48f001de12225 [buffer: eliminate the need to call
free_more_memory() in __getblk_slow()], no free_more_memory
function

Signed-off-by: Li RongQing <lirongqing@baidu.com>
---
 fs/buffer.c       | 2 +-
 fs/fs-writeback.c | 4 ----
 2 files changed, 1 insertion(+), 5 deletions(-)

diff --git a/fs/buffer.c b/fs/buffer.c
index cabc045f483d..58e199da8ca0 100644
--- a/fs/buffer.c
+++ b/fs/buffer.c
@@ -924,7 +924,7 @@ grow_dev_page(struct block_device *bdev, sector_t block,
 	struct page *page;
 	struct buffer_head *bh;
 	sector_t end_block;
-	int ret = 0;		/* Will call free_more_memory() */
+	int ret = 0;
 	gfp_t gfp_mask;
 
 	gfp_mask = mapping_gfp_constraint(inode->i_mapping, ~__GFP_FS) | gfp;
diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
index 471d863958bc..abafc9bd4622 100644
--- a/fs/fs-writeback.c
+++ b/fs/fs-writeback.c
@@ -1968,10 +1968,6 @@ void wb_workfn(struct work_struct *work)
 	current->flags &= ~PF_SWAPWRITE;
 }
 
-/*
- * Start writeback of `nr_pages' pages on this bdi. If `nr_pages' is zero,
- * write back the whole world.
- */
 static void __wakeup_flusher_threads_bdi(struct backing_dev_info *bdi,
 					 enum wb_reason reason)
 {
-- 
2.16.2

             reply	other threads:[~2018-06-29  8:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-29  8:31 Li RongQing [this message]
2018-07-19  3:22 ` 答复: [PATCH] fs: remove obsolete comment Li,Rongqing

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=1530261079-25068-1-git-send-email-lirongqing@baidu.com \
    --to=lirongqing@baidu.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.