netdev - Re: [RFC net-next 03/15] devlink: split out netlink code

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: <e350733f-d732-4ba6-a744-d77a37a237eb@intel.com>
Date:   Thu, 15 Dec 2022 10:45:48 -0800
From:   Jacob Keller <jacob.e.keller@...el.com>
To:     Jakub Kicinski <kuba@...nel.org>, <davem@...emloft.net>
CC:     <netdev@...r.kernel.org>, <edumazet@...gle.com>,
        <pabeni@...hat.com>, <jiri@...nulli.us>, <leon@...nel.org>
Subject: Re: [RFC net-next 03/15] devlink: split out netlink code



On 12/14/2022 6:01 PM, Jakub Kicinski wrote:
> Move out the netlink glue into a separate file.
> Leave the ops in the old file because we'd have to export a ton
> of functions. Going forward we should switch to split ops which
> will let us to put the new ops in the netlink.c file.
> 
Moving to split ops will also be a requirement for per-op policy right?

Thanks,
Jake