Re: [PATCH] zram: don't copy invalid compression algorithms

Sergey Senozhatsky
2015-09-08T05:04:04Z

On (09/08/15 13:50), Minchan Kim wrote:
[..]
> And it's straightforward/consistent to change the thing's state
> only if is successful.
>

what for? I provided several good reasons not to do this, because
it makes life easier for users. we added this check in Jun 25, 2015
while this functionality and scripts have been around for years, and
apparently now it's users' problem and they must go and do something.

seriously, what improvement this change brings in the first place?
what does it make better and for whom?

-ss