mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: liwp.linux@gmail.com
To: Fengguang Wu <fengguang.wu@intel.com>, Jan Kara <jack@suse.cz>,
	Andrew Morton <akpm@linux-foundation.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Johannes Weiner <jweiner@redhat.com>,
	linux-kernel@vger.kernel.org
Cc: liwp.linux@gmail.com, Wanpeng Li <liwp@linux.vnet.ibm.com>
Subject: [PATCH] unmapped quotes
Date: Sat, 12 May 2012 16:47:40 +0800	[thread overview]
Message-ID: <4fae23ca.68db440a.4bc9.22cc@mx.google.com> (raw)
In-Reply-To: <y>

From: Wanpeng Li <liwp.linux@gmail.com>

Signed-off-by: Wanpeng Li <liwp@linux.vnet.ibm.com>
---
 mm/page-writeback.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/mm/page-writeback.c b/mm/page-writeback.c
index 26adea8..2b317a3 100644
--- a/mm/page-writeback.c
+++ b/mm/page-writeback.c
@@ -1155,7 +1155,7 @@ static long bdi_min_pause(struct backing_dev_info *bdi,
  * balance_dirty_pages() must be called by processes which are generating dirty
  * data.  It looks at the number of dirty pages in the machine and will force
  * the caller to wait once crossing the (background_thresh + dirty_thresh) / 2.
- * If we're over `background_thresh' then the writeback threads are woken to
+ * If we're over 'background_thresh' then the writeback threads are woken to
  * perform some writeout.
  */
 static void balance_dirty_pages(struct address_space *mapping,
-- 
1.7.9.5


             reply	other threads:[~2012-05-12  8:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-12  8:47 liwp.linux [this message]
2012-05-12  9:02 ` Michael Tokarev
2012-05-12 11:26   ` Fengguang Wu
2012-05-12 14:09     ` Johannes Weiner
2012-05-13  2:18       ` Cong Wang
2012-05-12 14:32     ` Bernd Petrovitsch

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=4fae23ca.68db440a.4bc9.22cc@mx.google.com \
    --to=liwp.linux@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=jack@suse.cz \
    --cc=jweiner@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liwp@linux.vnet.ibm.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

all inboxes | Powered by JetHome®