lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 4 Oct 2022 08:33:18 +0200 From: Jiri Pirko <jiri@...nulli.us> To: Jakub Kicinski <kuba@...nel.org> Cc: Vadim Fedorenko <vadfed@...com>, Vadim Fedorenko <vfedorenko@...ek.ru>, Arkadiusz Kubalewski <arkadiusz.kubalewski@...el.com>, Jonathan Lemon <jonathan.lemon@...il.com>, Aya Levin <ayal@...dia.com>, netdev@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-clk@...r.kernel.org, Gal Pressman <gal@...dia.com> Subject: Re: [RFC PATCH v2 0/3] Create common DPLL/clock configuration API Mon, Oct 03, 2022 at 04:28:31PM CEST, kuba@...nel.org wrote: >On Sun, 2 Oct 2022 16:35:07 +0200 Jiri Pirko wrote: >>>> What I'm trying to say >>>> is, perhaps sysfs is a better API for this purpose. The API looks very >>>> neat and there is no probabilito of huge grow. >>> >>> "this API is nice and small" said everyone about every new API ever, >>> APIs grow. >> >> Sure, what what are the odds. > >The pins were made into full objects now, and we also model muxes. > >Vadim, could you share the link to the GH repo? > >What's your feeling on posting the latest patches upstream as RFC, >whatever state things are in right now? > >My preference would be to move the development to the list at this >stage, FWIW. I agree, that would be great.
Powered by blists - more mailing lists