Re: [PATCH 1/2] zram: pass gfp from zcomp frontend to backend

From: Andrew Morton
Date: Mon Nov 30 2015 - 19:10:12 EST


On Fri, 27 Nov 2015 13:23:13 +0900 Sergey Senozhatsky <sergey.senozhatsky.work@xxxxxxxxx> wrote:

> From: Minchan Kim <minchan@xxxxxxxxxx>
>
> 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 <minchan@xxxxxxxxxx>
> Acked-by: Sergey Senozhatsky <sergey.senozhatsky@xxxxxxxxx>

I changed this to signed-off-by:you. Documentation/SubmittingPatches
section 11 explains why ;)

(Hm, rule (c) is recursive. Nice!)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/