From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
hugh.dickins@tiscali.co.uk, ak@linux.intel.com,
Wu Fengguang <fengguang.wu@intel.com>
Subject: Re: [PATCH 0/2] mm hugetlb x86: add hugepage support to pagemap
Date: Wed, 09 Dec 2009 10:08:59 +0900 [thread overview]
Message-ID: <4B1EF8AB.6010806@ah.jp.nec.com> (raw)
In-Reply-To: <20091208143928.f3aa0ad2.akpm@linux-foundation.org>
> I kind of dislike the practice of putting all the changelog in patch
> [0/n] and then leaving the patches themselves practically
> unchangelogged. Because
Sorry, I agree.
>
> a) Someone (ie: me) needs to go and shuffle all the text around so
> that the information gets itself into the git record. We don't add
> changelog-only commits to git!
>
> b) Someone (ie: me) might decide to backport a subset of the patches
> into -stable. Now someone (ie: me) needs to carve up the changelogs
> so that the pieces which go into -stable still make standalone sense.
>
> I'm not sure that I did this particularly well in this case. Oh well.
>
>
> Please confirm that
> mm-hugetlb-fix-hugepage-memory-leak-in-walk_page_range.patch is
> suitable for a -stable backport without inclusion of
> mm-hugetlb-add-hugepage-support-to-pagemap.patch. I think it is.
>
I think that's OK.
Thanks,
Naoya Horiguchi
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2009-12-09 1:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 7:59 Naoya Horiguchi
2009-12-08 22:39 ` Andrew Morton
2009-12-09 1:08 ` Naoya Horiguchi [this message]
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=4B1EF8AB.6010806@ah.jp.nec.com \
--to=n-horiguchi@ah.jp.nec.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=hugh.dickins@tiscali.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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