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: <1444875266.2718.37.camel@perches.com> Date: Wed, 14 Oct 2015 19:14:26 -0700 From: Joe Perches <joe@...ches.com> To: "Moore, Robert" <robert.moore@...el.com> Cc: LABBE Corentin <clabbe.montjoie@...il.com>, "Zheng, Lv" <lv.zheng@...el.com>, "Wysocki, Rafael J" <rafael.j.wysocki@...el.com>, "lenb@...nel.org" <lenb@...nel.org>, "linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>, "devel@...ica.org" <devel@...ica.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] acpi: set return value to const char for some functions On Wed, 2015-10-14 at 20:53 +0000, Moore, Robert wrote: > In ACPICA, we tend to be very careful concerning the "const" keyword in order to avoid a phenomenon known as "const pollution". > > That is not to say that we won't use const in some limited cases. Please describe the effects of "const pollution". Why isn't it useful to update the functions that don't modify function pointer arguments to const? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists