Messages in this thread | | | Date | Wed, 16 Jan 2008 14:20:50 -0800 (PST) | From | Christoph Lameter <> | Subject | Re: Why is the kfree() argument const? |
| |
On Wed, 16 Jan 2008, Johannes Weiner wrote:
> So if I got it right and you actually modify the memory you only got a > const pointer to, you reach a level where you _have to_ break this > policy and cast to a non-const pointer, as it is currently done in > kfree(). No?
Correct and we have gcc 4.2 currently spitting out warnings because of casting to non const. Any idea how to convince gcc that this is okay?
| |