Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp3579216pxv; Mon, 12 Jul 2021 22:00:49 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwgi6lp3/e+0FyV+qZbqJP7pgsuYt1lzIXyjWtXznsr7GqJ0qWw2IgvtrAUonQxA58xtZFs X-Received: by 2002:a50:fb95:: with SMTP id e21mr3086478edq.65.1626152449343; Mon, 12 Jul 2021 22:00:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1626152449; cv=none; d=google.com; s=arc-20160816; b=TOHN0kMqMwQQSt+PTsbT6E1fKhDuGMebzPpjSIWNCdpmAfmWX18/RMbVWB2nzIZJ/d sFhu6LKFm+rK7fvioZEix9J2MAdnciT6x0Sloq7//DCLkF5XIPgCEQNWI3Xe8I/2NKoz Hk/NYG2v28MnQc4gATezAcKWPjpy98yFuPPYTMRnf3IlNNtlOFuMhky/dkUlxbedR5CL w1gpjfS7GiqcmZSQuoMlsIbs9+IdW/aOKvqcwWwv69FLajnwGLM5DeEUG31KZMXAkagw n4w62Al1L3oNu+897ASbNs5/pKbf/usYuX3vjQVbAqLLhkeTCocQ0AUDLX3BE+J+Rk+O t8yw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=c1vyIvkSZHY17EmhcroU3Q1dpN4joDFJsb4NlPBXiJc=; b=r8gxYqM21WHXk3dEZHl6u3P5/Px2Hl91dqWdDDVLuGG9N+ED2CIbesCgr7F3KchmF3 ajRIKd5rAW6g75t5q0zIqQFpzNV9xdtLAcWVW4UcCOCrE1oyJATw/nwtS08DQnXxZO15 bxNiSodvokCcXXiuPPK7hZIZVD9dy//9/KTMAia8sO4FE4Wz1NEzUD6RQtTF2tfn7K0m zU/txddjXCMD2O0V+4gnY5nUe9mMDcyanj9i9VJjeGwFfv+kIogq/S4BfT2J5fVu3wr5 6sKLbNY60+pageXlRIVqzREPVgtnNnOkAnSWxfVHg8JIBIs6qV6GrMUn+hHcsPpTR+ie q8Zg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id n26si20621722edb.197.2021.07.12.22.00.15; Mon, 12 Jul 2021 22:00:49 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231261AbhGMFBo (ORCPT + 99 others); Tue, 13 Jul 2021 01:01:44 -0400 Received: from mga11.intel.com ([192.55.52.93]:8072 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229470AbhGMFBn (ORCPT ); Tue, 13 Jul 2021 01:01:43 -0400 X-IronPort-AV: E=McAfee;i="6200,9189,10043"; a="207080215" X-IronPort-AV: E=Sophos;i="5.84,235,1620716400"; d="scan'208";a="207080215" Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 12 Jul 2021 21:58:54 -0700 X-IronPort-AV: E=Sophos;i="5.84,235,1620716400"; d="scan'208";a="492567823" Received: from mckumar-mobl.gar.corp.intel.com (HELO [10.215.202.204]) ([10.215.202.204]) by fmsmga003-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 12 Jul 2021 21:58:51 -0700 Subject: Re: [PATCH] net: wwan: iosm: switch from 'pci_' to 'dma_' API To: Christophe JAILLET , linuxwwan@intel.com, loic.poulain@linaro.org, ryazanov.s.a@gmail.com, johannes@sipsolutions.net, davem@davemloft.net, kuba@kernel.org Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org References: From: "Kumar, M Chetan" Message-ID: <754912a3-d1fe-516f-d64b-e8a70a93d570@intel.com> Date: Tue, 13 Jul 2021 10:28:48 +0530 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 7/11/2021 8:21 PM, Christophe JAILLET wrote: > The wrappers in include/linux/pci-dma-compat.h should go away. > > The patch has been generated with the coccinelle script below and has been > hand modified to replace GFP_ with a correct flag. > It has been compile tested. > > When memory is allocated in 'ipc_protocol_init()' GFP_KERNEL can be used > because this flag is already used a few lines above and no lock is > acquired in the between. > > When memory is allocated in 'ipc_protocol_msg_prepipe_open()' GFP_ATOMIC > should be used because this flag is already used a few lines above. Thanks, Reviewed-by: M Chetan Kumar Regards, Chetan