On Mon, 23.03.15 11:30, Peter Hutterer (peter.hutte...@who-t.net) wrote:
No point parsing the properties if we can't get the devnode to apply them
later. Plus, this makes future additions easier to slot in.
Hmm, Peter, this series was never pushed?
(Just making sure this is not forgotten...)
Hi
On Wed, Apr 8, 2015 at 7:41 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Mon, 23.03.15 11:30, Peter Hutterer (peter.hutte...@who-t.net) wrote:
No point parsing the properties if we can't get the devnode to apply them
later. Plus, this makes future additions easier to slot in.
On Wed, Apr 08, 2015 at 07:41:06PM +0200, Lennart Poettering wrote:
On Mon, 23.03.15 11:30, Peter Hutterer (peter.hutte...@who-t.net) wrote:
No point parsing the properties if we can't get the devnode to apply them
later. Plus, this makes future additions easier to slot in.
Hmm, Peter,
Hi
On Mon, Mar 23, 2015 at 2:30 AM, Peter Hutterer
peter.hutte...@who-t.net wrote:
No point parsing the properties if we can't get the devnode to apply them
later. Plus, this makes future additions easier to slot in.
---
src/udev/udev-builtin-keyboard.c | 17 +
1 file
No point parsing the properties if we can't get the devnode to apply them
later. Plus, this makes future additions easier to slot in.
---
src/udev/udev-builtin-keyboard.c | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/src/udev/udev-builtin-keyboard.c