Messages in this thread | | | Date | Tue, 1 May 2012 18:01:47 -0700 (PDT) | From | David Rientjes <> | Subject | Re: [RFC] vmalloc: add warning in __vmalloc |
| |
On Wed, 2 May 2012, Nick Piggin wrote:
> Because it needs to be an ongoing thing, which is caught as soon as the > developer writes some code, rather than continually audited for and fixed > up after the fact. There is not a good way to enforce this at compile time. > > The existing callers do need to be fixed too, of course. >
I'm asking that existing callers be fixed up before such a warning is introduced.
| |