Re: new gpiocharger driver

2021-09-24 Thread Klemens Nanni
On Thu, Sep 16, 2021 at 11:07:20AM +0200, Mark Kettenis wrote: > > Date: Thu, 16 Sep 2021 06:14:39 + > > From: Klemens Nanni > > > > On 5 September 2021 01:22:53 GMT+05:00, Klemens Nanni > > wrote: > > >Read a single GPIO pin indicating whether AC is plugged in or not. > > > > > >This

Re: new gpioleds driver

2021-09-24 Thread Klemens Nanni
On Thu, Sep 16, 2021 at 11:12:50AM +0200, Mark Kettenis wrote: > > Date: Thu, 16 Sep 2021 06:12:39 + > > From: Klemens Nanni > > > > On 3 September 2021 20:16:33 GMT+05:00, Klemens Nanni > > wrote: > > >Here is a tiny driver enabling machines such as the Pinebook Pro to > > >indicate

Re: sigwaitinfo(2) and sigtimedwait(2)

2021-09-24 Thread Stuart Henderson
On 2021/09/24 19:36, Rafael Sadowski wrote: > I'm trying to port the more KDE stuff so my question is from porter > perspective. > > I need sigwaitinfo(2)/sigtimedwait(2) and I found both functions in > lib/libc/gen/sigwait.c with the comment "need kernel to fill in more > siginfo_t bits first".

preferred #include guard idiom?

2021-09-24 Thread ropers
I'm looking at the #include guards in various .h files in /usr/include. There seem to be different (comment) idioms present at the bottom of those files/#include guards. For example: ctype.h: #endif /* !_CTYPE_H_ */ float.h: #endif /* _FLOAT_H_ */ err.h: #endif /* !_ERR_H_ */ curses.h:

sigwaitinfo(2) and sigtimedwait(2)

2021-09-24 Thread Rafael Sadowski
I'm trying to port the more KDE stuff so my question is from porter perspective. I need sigwaitinfo(2)/sigtimedwait(2) and I found both functions in lib/libc/gen/sigwait.c with the comment "need kernel to fill in more siginfo_t bits first". Is the comment still up to date? If no, is it possible