netdev - Re: [RFC PATCH v2 0/3] Create common DPLL/clock configuration API

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2bb59b66-ffb2-0bfe-83d5-a6ff606ca98e@novek.ru>
Date:   Mon, 3 Oct 2022 18:20:25 +0100
From:   Vadim Fedorenko <vfedorenko@...ek.ru>
To:     Jakub Kicinski <kuba@...nel.org>, Jiri Pirko <jiri@...nulli.us>,
        Vadim Fedorenko <vadfed@...com>
Cc:     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

On 03.10.2022 15:28, Jakub Kicinski 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?

I've already shared the link to Jiri.
> 
> What's your feeling on posting the latest patches upstream as RFC,
> whatever state things are in right now?
> 
I'll post RFC v3 once we agree on locking mechanics for pins. Right now there is 
no good solution AFAIU, discussions are in progress.

> My preference would be to move the development to the list at this
> stage, FWIW.

I got this point and I will follow it once we will have something ready.