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: <1344826002.22116.3.camel@cr0> Date: Mon, 13 Aug 2012 10:46:42 +0800 From: Cong Wang <amwang@...hat.com> To: Ben Hutchings <bhutchings@...arflare.com> Cc: netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>, Ian Campbell <Ian.Campbell@...rix.com> Subject: Re: [PATCH 1/2] net: move and rename netif_notify_peers() On Fri, 2012-08-10 at 20:01 +0100, Ben Hutchings wrote: > On Fri, 2012-08-10 at 16:14 +0800, Cong Wang wrote: > > I believe net/core/dev.c is a better place for netif_notify_peers(), > > because other net event notify functions also stay in this file. > > > > And rename it to netdev_notify_peers(). > [...] > > Is there a convention for using the 'netdev' vs 'netif' prefixes? > If not, I don't see the point in renaming just this one function. > The reason why I rename it is there are more functions named netdev_* than netif_* in net/core/dev.c. Also given that netdev_bonding_change() has netdev_ prefix too. I don't have strong opinions on this. Thanks. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists