[systemd-devel] [PATCH] udev: Adding zram to inappropriate block device

[Reindl Harald]

Am 06.02.2014 18:45, schrieb Greg KH:
> On Thu, Feb 06, 2014 at 04:54:59PM +0000, "Jóhann B. Guðmundsson" wrote:
>>
>> On 02/06/2014 03:39 PM, Greg KH wrote:
>>>>> Right now you have to decide before loading the module how many
>>>>> devices you want. And also when trying to use a device (any device),
>>>>> you have to look for one. The same issues as with loop.
>>> Given that the code doesn't have the ability to dynamically add/remove
>>> devices, I think we are stuck with this, right?
>>
>> This may come as a completely stupid question but if the code is expected
>> to be able to dynamically add/remove devices should not upstream ( kernel )
>> nack inclusion of zram until it does?
> 
> I don't think the code is expected to be able to do that, have you
> looked at it and seen where it does?

please re-read both posts
in the last one clearly a "not" fails

fixed version:
>> This may come as a completely stupid question but if the code is *not* expected
>> to be able to dynamically add/remove devices should not upstream ( kernel )
>> nack inclusion of zram until it does?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 246 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20140206/d72746ab/attachment.pgp>