On Wed, Jun 27, 2012 at 11:40:03AM -0400, Konrad Rzeszutek Wilk wrote: > On Tue, Jun 26, 2012 at 08:21:01PM -0700, Greg Kroah-Hartman wrote: > > On Wed, Jun 27, 2012 at 11:49:58AM +0900, Minchan Kim wrote: > > > Hi Greg, > > > > > > On 06/27/2012 11:43 AM, Greg Kroah-Hartman wrote: > > > > > > > On Wed, Jun 27, 2012 at 11:37:25AM +0900, Minchan Kim wrote: > > > >> On 06/26/2012 01:14 AM, Seth Jennings wrote: > > > >> > > > >>> This patch switches zcache and zram dependency to ZSMALLOC > > > >>> rather than X86. There is no net change since ZSMALLOC > > > >>> depends on X86, however, this prevent further changes to > > > >>> these files as zsmalloc dependencies change. > > > >>> > > > >>> Signed-off-by: Seth Jennings <sjenning@xxxxxxxxxxxxxxxxxx> > > > >> > > > >> Reviewed-by: Minchan Kim <minchan@xxxxxxxxxx> > > > >> > > > >> It could be merged regardless of other patches in this series. > > > > > > > > I already did :) > > > > > > > > > It would have been better if you send merge mail to Ccing people. > > > Anyway, Thanks! > > > > I do, for people on the cc: in the signed-off-by area of the patch. For > > me to manually add the people on the cc: of the email, I would have to > > modify git to add them to the commit somehow, sorry. > > Is that some other script you have that does that? I don't understand what you are asking here. My workflow is: - apply patches to a branch and test - if good, 'git format-patch' to create the patches - merge to my upstream branch and push out publically - run script on the patches generated by 'git format-patch' to say they have been applied. My custom script is the last thing there, that takes the patches, finds the email addresses in the patch, and notifies everyone. Does that explain things better? greg k-h -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>