From: David Rientjes <rientjes@google.com>
To: Wanpeng Li <liwp.linux@gmail.com>
Cc: Jiri Kosina <trivial@kernel.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Mel Gorman <mgorman@suse.de>, Minchan Kim <minchan@kernel.org>,
Hugh Dickins <hughd@google.com>,
linux-mm@kvack.org
Subject: Re: [PATCH] mm/vmscan: cleanup comment error in balance_pgdat
Date: Sat, 16 Jun 2012 19:11:09 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1206161908000.797@chino.kir.corp.google.com> (raw)
In-Reply-To: <20120617020355.GA2168@kernel>
On Sun, 17 Jun 2012, Wanpeng Li wrote:
> >acked, and then ask for it to be merged after an -rc1 release to avoid
> >lots of conflicts with other people's work.
>
> You mean trivial maintainer only pull trivial patches for -rc1 release ?
>
It all depends on how big your patch turns out to be; if it's sufficiently
large then it would probably be best to wait for -rc1, rebase your patch
to it, carry any acks that you have received, and ask it to be merged for
-rc2 to reduce conflicts with other code being pushed during the merge
window. Otherwise, just make a big patch and ask Andrew to carry it in
the -mm tree but make sure to base it off linux-next as it sits today.
You'll want to clone
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
--
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>
next prev parent reply other threads:[~2012-06-17 2:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 1:27 Wanpeng Li
2012-06-17 1:53 ` David Rientjes
2012-06-17 2:04 ` Wanpeng Li
2012-06-17 2:11 ` David Rientjes [this message]
2012-06-17 2:14 ` Wanpeng Li
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=alpine.DEB.2.00.1206161908000.797@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwp.linux@gmail.com \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--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