linux-kernel - Re: [PATCH 4/6] zram: describe device attrs in documentation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150312014726.GA948@swordfish>
Date:	Thu, 12 Mar 2015 10:47:26 +0900
From:	Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
To:	Minchan Kim <minchan@...nel.org>
Cc:	Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Nitin Gupta <ngupta@...are.org>, linux-kernel@...r.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
Subject: Re: [PATCH 4/6] zram: describe device attrs in documentation

On (03/12/15 10:33), Minchan Kim wrote:
> FYI, git-am got failed based on next-2015311 but patch tool worked.
> 

hm... oh, do you have this one applied

	From: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
	Subject: zram: do not let user enforce new device dev_id

	This patch forbids user to enforce device ids for newly added zram
	devices, as suggested by Minchan Kim.  There seems to be a little interest
	in this functionality and its use-cases are rather non-obvious.
	[..]

?

it does some documentation "rollbacks"

     Documentation/blockdev/zram.txt            |   20 +-

that is probably the reason.



> > +----            ------            -----------
> > +disksize          RO    disk size
> 
> disksize is RW
> 

ah, good catch! will send a trivial patch later.


Thanks for review!

	-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/