public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Zhihui Zhang <zzhsuny@gmail.com>
To: trivial@kernel.org, akpm@linux-foundation.org, mgorman@suse.de
Cc: kvm@vger.kernel.org
Subject: [PATCH] [mm] trivial fixes to long lines and typo in comment
Date: Sat, 29 Nov 2014 10:46:59 -0500	[thread overview]
Message-ID: <1417276019-17792-1-git-send-email-zzhsuny@gmail.com> (raw)

Well, the subject line says it all.

Signed-off-by: Zhihui Zhang <zzhsuny@gmail.com>
---
 include/linux/mmzone.h | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
index ffe66e3..cb668b7 100644
--- a/include/linux/mmzone.h
+++ b/include/linux/mmzone.h
@@ -966,7 +966,9 @@ static inline int zonelist_node_idx(struct zoneref *zoneref)
 }
 
 /**
- * next_zones_zonelist - Returns the next zone at or below highest_zoneidx within the allowed nodemask using a cursor within a zonelist as a starting point
+ * next_zones_zonelist - Returns the next zone at or below highest_zoneidx
+ *                       within the allowed nodemask using a cursor within
+ *                       a zonelist as a starting point
  * @z - The cursor used as a starting point for the search
  * @highest_zoneidx - The zone index of the highest zone to return
  * @nodes - An optional nodemask to filter the zonelist with
@@ -984,7 +986,8 @@ struct zoneref *next_zones_zonelist(struct zoneref *z,
 					struct zone **zone);
 
 /**
- * first_zones_zonelist - Returns the first zone at or below highest_zoneidx within the allowed nodemask in a zonelist
+ * first_zones_zonelist - Returns the first zone at or below highest_zoneidx
+ *                        within the allowed nodemask in a zonelist
  * @zonelist - The zonelist to search for a suitable zone
  * @highest_zoneidx - The zone index of the highest zone to return
  * @nodes - An optional nodemask to filter the zonelist with
@@ -1005,7 +1008,9 @@ static inline struct zoneref *first_zones_zonelist(struct zonelist *zonelist,
 }
 
 /**
- * for_each_zone_zonelist_nodemask - helper macro to iterate over valid zones in a zonelist at or below a given zone index and within a nodemask
+ * for_each_zone_zonelist_nodemask - helper macro to iterate over valid zones
+ *                                   in a zonelist at or below a given zone
+ *                                   index and within a nodemask
  * @zone - The current zone in the iterator
  * @z - The current pointer within zonelist->zones being iterated
  * @zlist - The zonelist being iterated
@@ -1021,7 +1026,8 @@ static inline struct zoneref *first_zones_zonelist(struct zonelist *zonelist,
 		z = next_zones_zonelist(++z, highidx, nodemask, &zone))	\
 
 /**
- * for_each_zone_zonelist - helper macro to iterate over valid zones in a zonelist at or below a given zone index
+ * for_each_zone_zonelist - helper macro to iterate over valid zones in a
+ *                          zonelist at or below a given zone index
  * @zone - The current zone in the iterator
  * @z - The current pointer within zonelist->zones being iterated
  * @zlist - The zonelist being iterated
@@ -1138,7 +1144,7 @@ extern unsigned long usemap_size(void);
 /*
  * We use the lower bits of the mem_map pointer to store
  * a little bit of information.  There should be at least
- * 3 bits here due to 32-bit alignment.
+ * 2 bits here due to 32-bit alignment.
  */
 #define	SECTION_MARKED_PRESENT	(1UL<<0)
 #define SECTION_HAS_MEM_MAP	(1UL<<1)
-- 
1.9.1


             reply	other threads:[~2014-11-29 15:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-29 15:46 Zhihui Zhang [this message]
2014-11-29 16:02 ` [PATCH] [mm] trivial fixes to long lines and typo in comment Mel Gorman
2014-11-29 21:08   ` Jiri Kosina

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=1417276019-17792-1-git-send-email-zzhsuny@gmail.com \
    --to=zzhsuny@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=kvm@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=trivial@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