| 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: <20110327.181414.260098631.davem@davemloft.net> Date: Sun, 27 Mar 2011 18:14:14 -0700 (PDT) From: David Miller <davem@...emloft.net> To: kurt.van.dijck@....be Cc: socketcan@...tkopp.net, netdev@...r.kernel.org Subject: Re: [PATCH] can: make struct proto const From: Kurt Van Dijck <kurt.van.dijck@....be> Date: Tue, 22 Mar 2011 20:00:38 +0100 > On Tue, Mar 22, 2011 at 07:27:25PM +0100, Oliver Hartkopp wrote: >> can_ioctl is the only reason for struct proto to be non-const. >> script/check-patch.pl suggests struct proto be const. >> >> Setting the reference to the common can_ioctl() in all CAN protocols directly >> removes the need to make the struct proto writable in af_can.c >> >> Signed-off-by: Kurt Van Dijck <kurt.van.dijck@....be> >> Signed-off-by: Oliver Hartkopp <socketcan@...tkopp.net> >> > Good idea to take this apart from my J1939 series. Applied, 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