[<prev] [next>] [day] [month] [year] [list]
Message-ID: <877fkfxmqk.fsf@rustcorp.com.au>
Date: Wed, 16 Dec 2015 10:56:11 +1030
From: Rusty Russell <rusty@...tcorp.com.au>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
Ingo Molnar <mingo@...nel.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
SergeySenozhatsky <sergey.senozhatsky@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Xunlei Pang <xlpang@...hat.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Rik van Riel <riel@...hat.com>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH 1/4] cpumask: Migrate 'alloc_cpumask_var()' users to 'zalloc_cpumask_var()'
Linus Torvalds <torvalds@...ux-foundation.org> writes:
> On Dec 7, 2015 8:13 PM, "Ingo Molnar" <mingo@...nel.org> wrote:
>>
>> One question: I'll remove all the non-zeroing variants, but would you be
> fine with
>> keeping the 'zalloc' naming? That's consistent with other allocation API
> patterns
>> across the kernel. There won't be any unsafe API left.
>
> Sure, I guess that won't hurt, and we could quietly start deprecating the
> zalloc pattern just to avoid the redundancy in the long run..
I like the zalloc naming, it's clear. But the series looks fine:
Acked-by: Rusty Russell <rusty@...tcorp.com.au>
Thanks,
Rusty.
--
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