[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150417013200.GD2412@swordfish>
Date: Fri, 17 Apr 2015 10:32:00 +0900
From: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Minchan Kim <minchan@...nel.org>,
Nitin Gupta <ngupta@...are.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCHv2 00/10] cleaned up on-demand device creation
On (04/17/15 10:00), Sergey Senozhatsky wrote:
> Date: Fri, 17 Apr 2015 10:00:24 +0900
> From: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
> To: Andrew Morton <akpm@...ux-foundation.org>, Minchan Kim
> <minchan@...nel.org>
> Cc: Nitin Gupta <ngupta@...are.org>, linux-kernel@...r.kernel.org, Sergey
> Senozhatsky <sergey.senozhatsky.work@...il.com>
> Subject: Re: [PATCHv2 00/10] cleaned up on-demand device creation
> User-Agent: Mutt/1.5.23 (2014-03-12)
>
> On (04/16/15 20:55), Sergey Senozhatsky wrote:
> > unfortunately, commit c72c6160d967ed26a0b136dbab337f821d233509
> > Author: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
> > Date: Wed Apr 15 16:15:55 2015 -0700
> >
> > zram: move compact_store() to sysfs functions area
> >
>
> Andrew, please ignore the whole series.
>
>
> I will send a separate patch to address the compaction issue shortly.
>
or simply revert c72c6160d967ed26a0b136dbab337f821d233509, which is
probably even better. there is no sense in moving compact_store to
a sysfs handlers logical code block anyway. there is simply no such
block there yet (logical code reorganization happens in a separate patch,
which was not merged into 4.1).
so I think reverting it is the best option for now.
$ git revert c72c6160d967ed26a0b136dbab337f821d233509
[master 211073e] Revert "zram: move compact_store() to sysfs functions area"
-ss
--
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