Messages in this thread | | | Subject | Re: [PATCH RFC v2] slab: introduce kmalloc_array | From | Xi Wang <> | Date | Sun, 12 Feb 2012 00:46:44 -0500 |
| |
On Feb 11, 2012, at 7:19 AM, Alexey Dobriyan wrote: > But there is no misuse. > > Both kaalloc(non-const, const) and kaalloc(const, non-const) are OK. > It's just first case happens more often.
Any k*alloc(const, non-const) example? I feel like in most cases it is the caller code that should get fixed, such as:
https://lkml.org/lkml/2012/2/10/135
- xi
| |