From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9A380C433EF for ; Fri, 11 Feb 2022 00:20:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346256AbiBKAU5 (ORCPT ); Thu, 10 Feb 2022 19:20:57 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:53274 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1346244AbiBKAUz (ORCPT ); Thu, 10 Feb 2022 19:20:55 -0500 Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5F02B5594; Thu, 10 Feb 2022 16:20:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1644538855; x=1676074855; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=e5IiG17cQUjJ9PQOtAwSdbXG1C8VuyC2rEhJR099Nh0=; b=CKOumQBxcF5ZMTqiM+NbGG2w10b7obDNAH4wV+Qv62oVb2GAExdFxbHT E9G5xVN37/aaf8OWhVbYFNNRwgBheYeB/GUo4j43sC11t0VbptYfSVK1Y jYrmmzdO0Wn/h0aYx+Z7EWuSJE2vcu9tuSQYVhr47s41otER/udhWTmQJ FJszQIsh+J1axg99dYqYt0JrWE9H3gFtUkUCmZMsNovYcG+5b7DDPGk4U BIIFRbSyskrPEo+vsAxj41EtFNGwI3VIaxmwEAhVnsVU6o89BgeTK03eh sIRtZQlGN1Ikvzr+iobUoTRRDkeULjEJiyDW7RGCRw5pm8xiqFJvLDeEB w==; X-IronPort-AV: E=McAfee;i="6200,9189,10254"; a="336046688" X-IronPort-AV: E=Sophos;i="5.88,359,1635231600"; d="scan'208";a="336046688" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Feb 2022 16:20:55 -0800 X-IronPort-AV: E=Sophos;i="5.88,359,1635231600"; d="scan'208";a="774072606" Received: from wlincolx-mobl.amr.corp.intel.com (HELO [10.212.86.106]) ([10.212.86.106]) by fmsmga005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Feb 2022 16:20:54 -0800 Message-ID: Date: Thu, 10 Feb 2022 18:20:53 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0 Thunderbird/91.5.0 Subject: Re: [PATCH 3/9] ASoC: Intel: bytcr_wm5102: use GFP_KERNEL Content-Language: en-US To: Julia Lawall , Cezary Rojewski , Hans de Goede Cc: alsa-devel@alsa-project.org, kernel-janitors@vger.kernel.org, Takashi Iwai , Jie Yang , Liam Girdwood , Mark Brown , linux-kernel@vger.kernel.org References: <20220210204223.104181-1-Julia.Lawall@inria.fr> <20220210204223.104181-4-Julia.Lawall@inria.fr> From: Pierre-Louis Bossart In-Reply-To: <20220210204223.104181-4-Julia.Lawall@inria.fr> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2/10/22 14:42, Julia Lawall wrote: > Platform_driver probe functions aren't called with locks held > and thus don't need GFP_ATOMIC. Use GFP_KERNEL instead. > > Problem found with Coccinelle. Thanks Julia, indeed it's the only case where GFP_ATOMIC is used for machine drivers. This was already present in the initial Android driver from Intel (2013) [1] and missed in the multiple passes to get this upstream. Acked-by: Pierre-Louis Bossart [1] https://github.com/lenovo-yt2-dev/android_kernel_lenovo_baytrail/blob/cm-12.1/sound/soc/intel/board/byt_bl_wm5102.c > > Signed-off-by: Julia Lawall > > --- > sound/soc/intel/boards/bytcr_wm5102.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/sound/soc/intel/boards/bytcr_wm5102.c b/sound/soc/intel/boards/bytcr_wm5102.c > index 504ef4cab111..8d8e96e3cd2d 100644 > --- a/sound/soc/intel/boards/bytcr_wm5102.c > +++ b/sound/soc/intel/boards/bytcr_wm5102.c > @@ -389,7 +389,7 @@ static int snd_byt_wm5102_mc_probe(struct platform_device *pdev) > bool sof_parent; > int ret; > > - priv = devm_kzalloc(dev, sizeof(*priv), GFP_ATOMIC); > + priv = devm_kzalloc(dev, sizeof(*priv), GFP_KERNEL); > if (!priv) > return -ENOMEM; > >