From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756021AbcG0MrB (ORCPT ); Wed, 27 Jul 2016 08:47:01 -0400 Received: from mail-wm0-f65.google.com ([74.125.82.65]:33488 "EHLO mail-wm0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754421AbcG0Mq7 (ORCPT ); Wed, 27 Jul 2016 08:46:59 -0400 User-agent: mu4e 0.9.17; emacs 24.5.1 From: Mathieu OTHACEHE To: Oliver Neukum Cc: Mathieu OTHACEHE , johan@kernel.org, gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org Subject: Re: [PATCH v2 03/22] usb: serial: ti_usb_3410_5052: Use kzalloc instead of kmalloc Message-ID: <87y44nntdn.fsf@gmail.com> In-reply-to: <1469606944.2408.0.camel@suse.com> Date: Wed, 27 Jul 2016 14:46:32 +0200 MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > in that case, where is the initialisation to 0 you avoid and hence > can remove from the code? Hi, In v1, kzalloc was useful to avoid wFlags initialisation to 0 : https://lkml.org/lkml/2016/5/12/139 In v2 wFlags initialisation has be removed so this patch has no purpose anymore, my bad. Thanks, Mathieu