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: <20230320181938.1b7e8139@kernel.org>
Date:   Mon, 20 Mar 2023 18:19:38 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     Stephen Hemminger <stephen@...workplumber.org>
Cc:     Florian Fainelli <f.fainelli@...il.com>, davem@...emloft.net,
        netdev@...r.kernel.org, edumazet@...gle.com, pabeni@...hat.com,
        jesse.brandeburg@...el.com, anthony.l.nguyen@...el.com,
        corbet@....net, linux-doc@...r.kernel.org
Subject: Re: [PATCH net-next] docs: networking: document NAPI

On Mon, 20 Mar 2023 17:48:40 -0700 Stephen Hemminger wrote:
> > On Thu, 16 Mar 2023 16:16:39 -0700 Florian Fainelli wrote:  
> > > Did it not stand for New API?    
> > 
> > I think it did. But we had extra 20 years of software development
> > experience and now agree that naming things "new" or "next" is
> > a bad idea? So let's pretend it stands for nothing. Or NAPI API ;)  
> 
> 
> Maybe just a footnote like:
>   [1] Was originally referred to as New API in 2.4 Linux.

👌️ let me find out how to make a footnote in sphinx

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ