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 E65FD41E38; Thu, 9 Mar 2023 11:33:29 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 80DE540ED7; Thu, 9 Mar 2023 11:33:29 +0100 (CET) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) by mails.dpdk.org (Postfix) with ESMTP id 113FC400D7 for ; Thu, 9 Mar 2023 11:33:28 +0100 (CET) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 425473200958; Thu, 9 Mar 2023 05:33:26 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Thu, 09 Mar 2023 05:33:26 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type: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=fm1; t= 1678358005; x=1678444405; bh=Wg/19yST4fGNEHjlLh2OlIsGBQpXxBUpxld +lb2lZYc=; b=S6nQK8QutGPOrC8liC0p1K8d8bBN2pBbSqr3QdzJ8G0WhwQII4t s9/33NIdypANN8NgcE7b0r6Dde9psqlTKv20WOjjaqPpe7QXvDn8uag6nTtEDvHn 60M0InhoNslfGDpKBIni/zY/x7Hh/5QpuOqI63evS6rxzopdB6aDEfTs/axR32yO 2HkcRDkpARGXI0vtWhHVvxCjHmHV9SH8NsHnC8zEB7xSD8+0jrGxxRovf2Ks/gYn ww4NRzrs1kEzngg6XDoiQ4ksrNuthOKnKSl00Mnm2nUHWDmSJPY6FlPsultmE3aD 2dQzm3+3avUE5o915Tw4ZxPXSqz9rhk6zYw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type: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=fm1; t= 1678358005; x=1678444405; bh=Wg/19yST4fGNEHjlLh2OlIsGBQpXxBUpxld +lb2lZYc=; b=Tf3OlZZbpeRg/kc1Otn80mux849TjkGUWk7FL3Mdl0dXZGOWOkJ h8mWBA+Fk2rBniotZnt38Ok82tzZsU90r+nH94C2A2pPgM8eVf1g9t8rn0b3Aymv GLE7N640wPvFMEv50C1S3WvOW0cIcqLaTS03JbEDQ4tyMJJclY2tJXFVmVzuvqYd Pp+mHTLeZqjboeXasGMQ896HR9hgqnS+49lWIxyfoTPUV3xBprSbS3nvzEnLJFIF f0tlQOuztkxUGM06kBcyJb9V/T88grhJC+SEf7/78Khe0JkoDri2pd6VnQ/7wT55 YJgtpct3er0uW/BK6CeAMf3InYtOPknnmGQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdduiedgudeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthhqredttddtjeenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpeegtddtleejjeegffekkeektdejvedtheevtdekiedvueeuvdei uddvleevjeeujeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 9 Mar 2023 05:33:24 -0500 (EST) From: Thomas Monjalon To: David Marchand , jerinj@marvell.com Cc: Morten =?ISO-8859-1?Q?Br=F8rup?= , rmody@marvell.com, shshaikh@marvell.com, dev@dpdk.org Subject: Re: [PATCH v7 1/4] net/bnx2x: fix warnings about rte_memcpy lengths Date: Thu, 09 Mar 2023 11:33:23 +0100 Message-ID: <9073737.CDJkKcVGEf@thomas> In-Reply-To: References: <20221202153432.131023-1-mb@smartsharesystems.com> <98CBD80474FA8B44BF855DF32C47DC35D87724@smartserver.smartshare.dk> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 09/03/2023 11:25, David Marchand: > On Thu, Feb 9, 2023 at 5:49=E2=80=AFPM Morten Br=C3=B8rup wrote: > > > > PING bnx2x maintainers. Care to review this bugfix, so it can be includ= ed in 23.03? > > >=20 > Still no luck in getting attention from bnx2x maintainers. > One option is to declare this driver as UNMAINTAINED and disable its > compilation when the memcpy annotations are finalised and merged in a > next release. Yes that's an option. Jerin, what is your opinion?