| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
Follow-up for 02f7f8aa4f1d0b7a24ee3cd5685a791771d9ded5
This deserves some highlight.
Addresses https://github.com/systemd/systemd/pull/28597#discussion_r1288592726
|
|
|
|
|
|
|
|
|
| |
Follow-up for 02f7f8aa4f1d0b7a24ee3cd5685a791771d9ded5
Addresses https://github.com/systemd/systemd/pull/28597#discussion_r1288591215
> this is pretty unnecessary, battery_read_capacity_percentage()
debug logs on its own about this already, in more detailed way?
|
|
|
|
|
|
| |
The logs would give no hint about the answer to most interesting question: why
we decided to return true or false from the program. If we find batteries
that are low or uncertain, log at info level.
|
| |
|
| |
|
|
|
|
|
|
|
| |
battery state
Let's avoid assuming a low battery battery state if in doubt. That
means, handle errors reading battery state gracefully.
|
|
|
|
|
|
|
|
|
|
| |
This moves a first batch of functions from sleep-config.[ch] over to
battery-util.[ch].
In the long run we should probably move even more stuff over, i.e.
anything that deals with the battery sysfs driver interface.
No code change.
|
|
No code change, just some splitting out of the relevant code from
udev-util.[ch].
This makes sense on its own, but is also prepartion to move the code
that checks for low battery state into battery-util.[ch], too.
|