From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id B9FFA41BDD;
	Sun,  5 Feb 2023 18:36:28 +0100 (CET)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 9B72C40A89;
	Sun,  5 Feb 2023 18:36:28 +0100 (CET)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com
 [66.111.4.28]) by mails.dpdk.org (Postfix) with ESMTP id A1EA940A7D
 for <dev@dpdk.org>; Sun,  5 Feb 2023 18:36:27 +0100 (CET)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45])
 by mailout.nyi.internal (Postfix) with ESMTP id 5A0745C02E2;
 Sun,  5 Feb 2023 12:36:27 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162])
 by compute5.internal (MEProxy); Sun, 05 Feb 2023 12:36:27 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
 cc:cc:content-transfer-encoding:content-type:date:date:from:from
 :in-reply-to:in-reply-to:message-id:mime-version:references
 :reply-to:sender:subject:subject:to:to; s=fm3; t=1675618587; x=
 1675704987; bh=Yid4iI0Ibrnu3dnweyXbvuBGngLhii4RYMrkmE7jHJA=; b=d
 nl/QV1mDufjItfWnre+diCLONBhGbRYADNBRTE4zHokTbrufkKPdSXOc2EgqpEE1
 XC2NVhuGAnVc/cRhR8xTZMPOscv0FFM0z8jrkkU2GhsC3peaj57UrEvu8KiWauYi
 sr2YvfHN8PMUn5FB2A2eWAJg8ftmQGuGp1Pj1BHERJpj1EQ4IQpIsel70n6MyYNz
 ve7mDx8MlXOKP4SeW/tYHhksJb5r7YfpAeW8cVXWXuTvpFYVOtmjA/Pquq1goauS
 S9aRvcPnCLfz9aU42S0jhiT9lDp0X4PEANpIpV/A6x0CUmNb2z6O7C/EhQrrZH8V
 SmS7M8RI615lqdZqx0t2w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:cc:content-transfer-encoding
 :content-type:date:date:feedback-id:feedback-id:from:from
 :in-reply-to:in-reply-to:message-id:mime-version:references
 :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy
 :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1675618587; x=
 1675704987; bh=Yid4iI0Ibrnu3dnweyXbvuBGngLhii4RYMrkmE7jHJA=; b=B
 kEMVCl0JhD7LuJlikCzYZG5rM5hBOOo4kDNUlfXsFRpdaeA7JTr5NLzCI+CT/NNJ
 RlQQdoqm/PFk0k7kWwY2SRVdSbr+xYvCiQus+ivV6tSX90Zuwsmmt6ByrxddAPk+
 onOQq9H75cqDxKZe1B5cPvsy88DKSDDItRT7I82XDIHKNPyjsOm4/kjU54A6sPTD
 7N/y/FU0zFM2FeiAgG1WMlaYyvGUmLni1jtDBFiJ1T0DrOdz5XLQf824HKeNmCWn
 ov3p7UBZEl6WE4FjZ3zyXlagTlDK5+w55T9k0f+atOPG5JEsiuiBlVH2SwSKL7k1
 FIW5JMKpCuQ38qK0IHCiw==
X-ME-Sender: <xms:G-nfY8auZGdbtpKZvUyuPXH8A3xHBmXIwfrx-cjmOlFtgQW4TOLtKg>
 <xme:G-nfY3ZqYpXNXvD-Da5VFOJ7pQN84pt3uDl5F2jitIA1iiihZn6G2bI14BYU9upMn
 EuRLZkjHLoRFSS6yg>
X-ME-Received: <xmr:G-nfY2-wtXbLWSZPQkRzunsP4TEcA7I6UynB77nuF6nAQpzg0nQ6PSV-Z9lAuTqcQSkNh1u5kxVfuZQpVklwgSaaIg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudeggedguddtvdcutefuodetggdotefrod
 ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh
 necuuegrihhlohhuthemuceftddtnecunecujfgurhephffvvefufffkjghfggfgtgesth
 furedttddtvdenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgr
 shesmhhonhhjrghlohhnrdhnvghtqeenucggtffrrghtthgvrhhnpeejjefffffgffekfe
 fflefgkeelteejffelledugefhheelffetheevudffudfgvdenucffohhmrghinhepughp
 ughkrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh
 homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth
X-ME-Proxy: <xmx:G-nfY2pFF_UjCBkbeLxEMFWN6Y7c87RYEUtyZt_hrMKQ2RJ0fjLyqg>
 <xmx:G-nfY3qOQWk1gyCfkBSBEo3xYCyu2fFMoEHu1ZbrPsWrS5gcR_06vQ>
 <xmx:G-nfY0TiSVxdzqqPLcaLEMaQ52JfSbOteEazd_c6KcZF2WdoBCyc1Q>
 <xmx:G-nfYwDUxQUYbOjGiY1l07M54Lnf57uwwJzEnplxfpPVDctrVSnZ8A>
Feedback-ID: i47234305:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun,
 5 Feb 2023 12:36:26 -0500 (EST)
From: Thomas Monjalon <thomas@monjalon.net>
To: Leonid Bloch <lb.workbox@gmail.com>
Cc: dev@dpdk.org, ferruh.yigit@amd.com
Subject: Re: [PATCH dpdk-kmods] linux/igb_uio: Adjust functions to the current
 kernel API
Date: Sun, 05 Feb 2023 18:36:24 +0100
Message-ID: <1886759.taCxCBeP46@thomas>
In-Reply-To: <20221020130044.17710-1-lb.workbox@gmail.com>
References: <20221020130044.17710-1-lb.workbox@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org

20/10/2022 15:00, Leonid Bloch:
> After commit 7968778914e53788a01c2dee2692cab157de9ac0 in the upstream
> kernel (v5.18+) The functions pci_set_dma_mask() and
> pci_set_consistent_dma_mask() are deprecated. Replacing them with the
> new substitute (to avoid a compilation error).
> 
> Signed-off-by: Leonid Bloch <lb.workbox@gmail.com>
> ---
> -	err = pci_set_dma_mask(dev,  DMA_BIT_MASK(64));
> +	err = dma_set_mask(&dev->dev,  DMA_BIT_MASK(64));
[...]
> -	err = pci_set_consistent_dma_mask(dev, DMA_BIT_MASK(64));
> +	err = dma_set_coherent_mask(&dev->dev, DMA_BIT_MASK(64));


The patch from Ferruh is simplifying the code:
https://patches.dpdk.org/project/dpdk/patch/20221216115732.3552650-1-ferruh.yigit@amd.com/