From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 3C02546211 for ; Thu, 13 Feb 2025 11:02:17 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 38DE542F04; Thu, 13 Feb 2025 11:02:17 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 267CF42EF1 for ; Thu, 13 Feb 2025 11:02:15 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1739440934; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=T0uD11qwNbAPYnyDld84EiFf8hW8V0eqYSGoCW6EIwI=; b=S0UYfGXO7aka/Bw5lG3qb9XeIW47TJW7QFL0ORo5MtFsdNo71iA0vXXb0Pp1cIJhD8WCUx CspbN2Kz5PSZhwIqTKxs4Ko8etFm+Q7aNN0sxsYHVKZ0YxzW12CKRtBvfO65/5OEcQbMHH 3ejlToQ+iqL9Cl0Ci66CNAjJmLVGru4= Received: from mx-prod-mc-08.mail-002.prod.us-west-2.aws.redhat.com (ec2-35-165-154-97.us-west-2.compute.amazonaws.com [35.165.154.97]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-632-dTT4SxM4Od23_n2axxeuSw-1; Thu, 13 Feb 2025 05:02:12 -0500 X-MC-Unique: dTT4SxM4Od23_n2axxeuSw-1 X-Mimecast-MFC-AGG-ID: dTT4SxM4Od23_n2axxeuSw Received: from mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.93]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-08.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id F2A5D1800872; Thu, 13 Feb 2025 10:02:11 +0000 (UTC) Received: from rh.Home (unknown [10.45.224.21]) by mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 7CEBC1800365; Thu, 13 Feb 2025 10:02:10 +0000 (UTC) From: Kevin Traynor To: Andre Muezerie Cc: Ajit Khaparde , dpdk stable Subject: patch 'net/bnxt: fix indication of allocation' has been queued to stable release 24.11.2 Date: Thu, 13 Feb 2025 09:58:31 +0000 Message-ID: <20250213095933.362078-64-ktraynor@redhat.com> In-Reply-To: <20250213095933.362078-1-ktraynor@redhat.com> References: <20250213095933.362078-1-ktraynor@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.93 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: LdpO2aiUciA8gXUnCY2cyjd9dh4ZAUHw4lE06lBR5l0_1739440932 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Hi, FYI, your patch has been queued to stable release 24.11.2 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 02/17/25. So please shout if anyone has objections. Also note that after the patch there's a diff of the upstream commit vs the patch applied to the branch. This will indicate if there was any rebasing needed to apply to the stable branch. If there were code changes for rebasing (ie: not only metadata diffs), please double check that the rebase was correctly done. Queued patches are on a temporary branch at: https://github.com/kevintraynor/dpdk-stable This queued commit can be viewed at: https://github.com/kevintraynor/dpdk-stable/commit/ae99f14c94a9d384be03ab8045fe2670fc074015 Thanks. Kevin --- >From ae99f14c94a9d384be03ab8045fe2670fc074015 Mon Sep 17 00:00:00 2001 From: Andre Muezerie Date: Fri, 17 Jan 2025 12:51:33 -0800 Subject: [PATCH] net/bnxt: fix indication of allocation MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit [ upstream commit 8531f9ba0062032454121f4959cd3d495cd4147e ] When experimenting with the -std=c2x compiler option the error below popped up: ../drivers/net/bnxt/tf_core/tf_sram_mgr.c:952:39: error: incompatible types when assigning to type ‘_Bool *’ from type ‘_Bool’ The code indicates that the intention was to assign false to the bool being pointed to, not to the pointer itself. Fixes: 37ff91c158a3 ("net/bnxt: add SRAM manager model") Signed-off-by: Andre Muezerie Acked-by: Ajit Khaparde --- drivers/net/bnxt/tf_core/tf_sram_mgr.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/net/bnxt/tf_core/tf_sram_mgr.c b/drivers/net/bnxt/tf_core/tf_sram_mgr.c index 87e8882fed..0dffd74cd5 100644 --- a/drivers/net/bnxt/tf_core/tf_sram_mgr.c +++ b/drivers/net/bnxt/tf_core/tf_sram_mgr.c @@ -950,5 +950,5 @@ int tf_sram_mgr_is_allocated(void *sram_handle, tf_sram_bank_2_str(parms->bank_id)); - parms->is_allocated = false; + *parms->is_allocated = false; goto done; } @@ -965,5 +965,5 @@ int tf_sram_mgr_is_allocated(void *sram_handle, TFP_DRV_LOG(ERR, "block not found in list 0x%x\n", parms->sram_offset); - parms->is_allocated = false; + *parms->is_allocated = false; goto done; } -- 2.48.1 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2025-02-12 17:29:41.326701888 +0000 +++ 0064-net-bnxt-fix-indication-of-allocation.patch 2025-02-12 17:29:34.393946186 +0000 @@ -1 +1 @@ -From 8531f9ba0062032454121f4959cd3d495cd4147e Mon Sep 17 00:00:00 2001 +From ae99f14c94a9d384be03ab8045fe2670fc074015 Mon Sep 17 00:00:00 2001 @@ -8,0 +9,2 @@ +[ upstream commit 8531f9ba0062032454121f4959cd3d495cd4147e ] + @@ -19 +20,0 @@ -Cc: stable@dpdk.org