[systemd-devel] [PATCH] hwdb: Add Thinkpad X1 carbon 3rd gen to 70-pointingstick.hwdb

2015-09-14 Thread Hans de Goede
Like many other recent thinkpads the factory default pointingstick sensitivity on these devices is quite low, making the pointingstick very slow in moving the cursor. This extends the existing hwdb rules for tweaking the sensitivity to also apply to the X1 carbon 3rd gen model. BugLink: https://b

Re: [systemd-devel] [PATCH] hwdb: Add Thinkpad X1 carbon 3rd gen to 70-pointingstick.hwdb

2015-09-14 Thread Daniel Mack
On 09/14/2015 02:16 PM, Hans de Goede wrote: > Like many other recent thinkpads the factory default pointingstick > sensitivity on these devices is quite low, making the pointingstick > very slow in moving the cursor. > > This extends the existing hwdb rules for tweaking the sensitivity to > also

Re: [systemd-devel] [PATCH] hwdb: Add Thinkpad X1 carbon 3rd gen to 70-pointingstick.hwdb

2015-09-14 Thread Hans de Goede
Hi, On 14-09-15 14:28, Daniel Mack wrote: On 09/14/2015 02:16 PM, Hans de Goede wrote: Like many other recent thinkpads the factory default pointingstick sensitivity on these devices is quite low, making the pointingstick very slow in moving the cursor. This extends the existing hwdb rules for

Re: [systemd-devel] [PATCH] hwdb: Add Thinkpad X1 carbon 3rd gen to 70-pointingstick.hwdb

2015-09-14 Thread systemd github import bot
Patchset imported to github. To create a pull request, one of the main developers has to initiate one via: -- Generated by https://github.com/haraldh/mail2git

Re: [systemd-devel] tmp.mount inactive => /tmp not mounted

2015-09-14 Thread Aaron_Wright
Andrei Borzenkov wrote on 09/12/2015 12:37:03 AM: > 12.09.2015 03:51, aaron_wri...@selinc.com пишет: > > I recently switched to using systemd in my initrd, and nearly everything > > works fine, expect now the system comes up without /tmp being mounted > > correctly. I'm not sure where to start lo

[systemd-devel] Incorrect use return value of mount_one in mount_setup_early/mount_setup?

2015-09-14 Thread cee1
Hi all, mount_one will return 1 if a mount action is performed; 0 for no mount performed; and <0 for an error occurred. Right? In mount_setup, we have the following logic: """ for (i = 0; i < ELEMENTSOF(mount_table); i ++) { int j; j = mount_one(mount_table + i, loaded_policy);