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
| ||
|
Message-ID: <Y712uDIgr/f1vveL@nanopsycho> Date: Tue, 10 Jan 2023 15:31:20 +0100 From: Jiri Pirko <jiri@...nulli.us> To: Jakub Kicinski <kuba@...nel.org> Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com, pabeni@...hat.com, jacob.e.keller@...el.com Subject: Re: [PATCH net-next 13/14] devlink: add by-instance dump infra Mon, Jan 09, 2023 at 08:49:49PM CET, kuba@...nel.org wrote: >On Sat, 7 Jan 2023 10:23:48 +0100 Jiri Pirko wrote: >> Hmm. >> 1) What is wrong of having: >> .dumpit = devlink_instance_iter_dumpit >> instead of >> .dumpit = devlink_instance_iter_dump >> ? >> How exactly that decreases readability? > >The "it" at the end of the function name is there because do is a C >keyword, so we can't call the do callback do, we must call it doit. > >The further from netlink core we get the more this is an API wart >and the less it makes sense. >instance iter dump is closer to plain English. Hmm, I guess if you are not happy about the callback name, you should change it, to ".dump" in this case. My point the the naming consistency between the callback name and the function assigned. But nevermind.
Powered by blists - more mailing lists