lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1206161908000.797@chino.kir.corp.google.com>
Date:	Sat, 16 Jun 2012 19:11:09 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Wanpeng Li <liwp.linux@...il.com>
cc:	Jiri Kosina <trivial@...nel.org>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Mel Gorman <mgorman@...e.de>, Minchan Kim <minchan@...nel.org>,
	Hugh Dickins <hughd@...gle.com>, linux-mm@...ck.org
Subject: Re: [PATCH] mm/vmscan: cleanup comment error in balance_pgdat

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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ