On (11/30/15 16:10), Andrew Morton wrote:
> > From: Minchan Kim <minc...@kernel.org>
> >
> > Each zcomp backend uses own gfp flag but it's pointless
> > because the context they could be called is driven by upper
> > layer(ie, zcomp frontend). As well, zcomp frondend could
> > call them in different context. One context(ie, zram init part)
> > is it should be better to make sure successful allocation
> > other context(ie, further stream allocation part for accelarating
> > I/O speed) is just optional so let's pass gfp down from driver
> > (ie, zcomp frontend) like normal MM convention.
> >
> > [sergey: add missing __vmalloc zero and highmem gfps]
> > Signed-off-by: Minchan Kim <minc...@kernel.org>
> > Acked-by: Sergey Senozhatsky <sergey.senozhat...@gmail.com>
>
> I changed this to signed-off-by:you. Documentation/SubmittingPatches
> section 11 explains why ;)
Thank you.
> (Hm, rule (c) is recursive. Nice!)
-ss
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
