linux-kernel - Re: [PATCH v2 1/4] Add ff-memless-next driver

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: <1651798.4YaLXnucpJ@geidi-prime>
Date:	Mon, 24 Feb 2014 02:54:11 +0100
From:	Michal Malý <madcatxster@...fuk.cz>
To:	Anssi Hannula <anssi.hannula@....fi>
Cc:	linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
	dmitry.torokhov@...il.com, elias.vds@...il.com, jkosina@...e.cz,
	simon@...gewell.org
Subject: Re: [PATCH v2 1/4] Add ff-memless-next driver

I forgot to comment on this:
> Stopped effects should still be able to be updated.
Fair enough. I could not find a definitive answer to what is expected behavior 
in this case. As far as I can tell, there are following cases:
- Effects with no duration and delay: they shall be updated right away.
- Effects with delay: updated parameters shall be sent to the device at the 
correct time.
- "Expired" effects with finite duration - ??? I assumed that effects with 
finite duration that have already finished playing cannot be updated because 
it does not seem to make much sense to do so. Shall such an effect be 
restarted when it is updated? Is there any guideline I should stick to I am 
not aware of?

Michal M.
--
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/