On Sat, Feb 24, 2018 at 11:31 AM, Ognjen Galić <smclt30p@xxxxxxxxx> wrote: > On Sat, Feb 24, 2018 at 10:07:20AM +0100, Rafael J. Wysocki wrote: >> On Fri, Feb 23, 2018 at 6:21 PM, Andy Shevchenko >> <andy.shevchenko@xxxxxxxxx> wrote: >> > On Sat, Feb 10, 2018 at 10:48 AM, Ognjen Galić <smclt30p@xxxxxxxxx> wrote: >> > >> >> Do you guys want me to send in another revision of the patch with some >> >> documentation on the sysfs API? >> > >> > I noticed I didn't apply it because of some pending changes discussed, >> > perhaps this one above. >> > >> > So, definitely please send a new version which addresses comments. >> >> No, it actually has been applied already. > > So it has been queued up for 4.17? Yes, it has. > If it has, that is awesome! Thanks! No biggie. That said, I would like you to send a follow-up patch moving the definitions of the charge_start_threshold and charge_stop_threshold attributes to the power supply core as requested by Sebastian and documenting them. Of course, it still needs to be possible to add/remove them on demand after registering the power supply to cover the use case at hand AFAICS. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
