From: Coywolf Qi Hunt <coywolf@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org, clameter@sgi.com
Subject: Re: + swap-migration-v5-lru-operations-tweaks.patch added to -mm tree
Date: Mon, 7 Nov 2005 13:15:57 +0800 [thread overview]
Message-ID: <2cd57c900511062115n5975fba7v@mail.gmail.com> (raw)
In-Reply-To: <200511010521.jA15Lpsm016996@shell0.pdx.osdl.net>
2005/11/1, akpm@osdl.org <akpm@osdl.org>:
>
> The patch titled
>
> swap-migration-v5-lru-operations-tweaks
>
> has been added to the -mm tree. Its filename is
>
> swap-migration-v5-lru-operations-tweaks.patch
>
>
> From: Andrew Morton <akpm@osdl.org>
>
> Cc: Christoph Lameter <clameter@sgi.com>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
> ---
>
> include/linux/mm_inline.h | 4 +---
> mm/vmscan.c | 6 +++---
> 2 files changed, 4 insertions(+), 6 deletions(-)
>
> diff -puN include/linux/mm_inline.h~swap-migration-v5-lru-operations-tweaks include/linux/mm_inline.h
> --- devel/include/linux/mm_inline.h~swap-migration-v5-lru-operations-tweaks 2005-10-31 21:21:48.000000000 -0800
> +++ devel-akpm/include/linux/mm_inline.h 2005-10-31 21:21:48.000000000 -0800
> @@ -44,8 +44,7 @@ del_page_from_lru(struct zone *zone, str
> *
> * - zone->lru_lock must be held
> */
> -static inline int
> -__isolate_lru_page(struct zone *zone, struct page *page)
> +static inline int __isolate_lru_page(struct zone *zone, struct page *page)
> {
> if (TestClearPageLRU(page)) {
> if (get_page_testone(page)) {
My curiosity, why we do this when the former is friendly to grep? Any
coding style document about this?
--
Coywolf Qi Hunt
http://sosdg.org/~coywolf/
next parent reply other threads:[~2005-11-07 5:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200511010521.jA15Lpsm016996@shell0.pdx.osdl.net>
2005-11-07 5:15 ` Coywolf Qi Hunt [this message]
2005-11-07 6:17 ` + swap-migration-v5-lru-operations-tweaks.patch added to -mm tree Andrew Morton
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=2cd57c900511062115n5975fba7v@mail.gmail.com \
--to=coywolf@gmail.com \
--cc=akpm@osdl.org \
--cc=clameter@sgi.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 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.