Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1470093
| From | Petr Mladek <pmladek@suse.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v6 20/20] thermal/intel_powerclamp: Convert the kthread to kthread worker API |
| Date | 2016-08-25 14:00 +0200 |
| Message-ID | <sa1kt-qZ-9@gated-at.bofh.it> (permalink) |
| References | <rnRdL-3Ro-3@gated-at.bofh.it> <rnRdN-3Ro-51@gated-at.bofh.it> <s9YmB-71V-27@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu 2016-08-25 10:33:17, Sebastian Andrzej Siewior wrote: > On 2016-04-14 17:14:39 [+0200], Petr Mladek wrote: > > Kthreads are currently implemented as an infinite loop. Each > > has its own variant of checks for terminating, freezing, > > awakening. In many cases it is unclear to say in which state > > it is and sometimes it is done a wrong way. > > What is the status of this? This is the last email I received and it is > from April. There were still some discussions about the kthread worker API. Anyway, the needed kthread API changes are in Andrew's -mm tree now and will be hopefully included in 4.9. I did not want to send the patches using the API before the API changes are upstream. But I could send the two intel_powerclamp patches now if you are comfortable with having them on top of the -mm tree or linux-next. Best Regards, Petr
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [PATCH v6 20/20] thermal/intel_powerclamp: Convert the kthread to kthread worker API Sebastian Andrzej Siewior <bigeasy@linutronix.de> - 2016-08-25 10:40 +0200 Re: [PATCH v6 20/20] thermal/intel_powerclamp: Convert the kthread to kthread worker API Sebastian Andrzej Siewior <bigeasy@linutronix.de> - 2016-08-25 13:50 +0200 Re: [PATCH v6 20/20] thermal/intel_powerclamp: Convert the kthread to kthread worker API Petr Mladek <pmladek@suse.com> - 2016-08-25 14:00 +0200
csiph-web