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 C91D8A0545; Wed, 29 Jun 2022 09:11:02 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6BBFE400D7; Wed, 29 Jun 2022 09:11:02 +0200 (CEST) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by mails.dpdk.org (Postfix) with ESMTP id C9B6540042 for ; Wed, 29 Jun 2022 09:11:00 +0200 (CEST) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 6D6B65C024A; Wed, 29 Jun 2022 03:10:58 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Wed, 29 Jun 2022 03:10:58 -0400 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=fm2; t=1656486658; x= 1656573058; bh=PsmrT+I4gug5ms1+FEuf/AsP2EspECFTGDJthfJ4B7I=; b=f D31LvVJXJejh8kZqtX9aCSFuKQYMmcXhLl8U7u9cdcwHmXbzmI2upMyya/pPSScJ Vjclj0vXEpce2VO1PhnBnNeUXXKIlPQL1weep+qMtEnfEBAFbpok3ooYz+uD/VLp voGy2uMsA2/zMZFEXvxRNqFiOrTT6NdoQQB+m83DAFUWTGwuFpamJ7948MoaA+Wh in5Ot1fFqpq+BjHZd3omcR+5F3BmsR0hBblnbBu8w1kBodt0Go0RRkkoDxUyMKAV I487VDzMwCdvrzwzKF1jGIliVuhjXkUPNqVGkjS1XAXs819mQk62FwxY7Hoq7bdW 06+pC0wfcEyVCUMEVJpGQ== 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=fm2; t=1656486658; x= 1656573058; bh=PsmrT+I4gug5ms1+FEuf/AsP2EspECFTGDJthfJ4B7I=; b=L rGFwRAxsel3D9Dzzva3OF52nKPojQDHbTzDCA+SC7BTUZQOkB7sZCfgIJOoH5ZyA uptpK+mbIWcJB+BCCH7uLoDsshg76cITpxWhh6U7AfwfsYl0nFVySOUoEDQ3DmRC ScFWCJ5EhlQ/eJrG4SlXtD8F8G+G33uDRJO3uj2AvKWU4Ozi95CWyntl1okqg57v LyciieUfSPqU0TTIMidgPsTL4+UTGVrf7rNZtyxuc2sIxtC7zSNaOt4A87kvwX8y HT7kxbvrHvcq2KSa2wELySkjueIKLPOePT3BwRqb9OHS3f4ctgJdAHJ0oA+pR8Jy ia4uTAyiqZLXWXezqVuWA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrudegkedgudduhecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvfevufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhho mhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqne cuggftrfgrthhtvghrnheptdejieeifeehtdffgfdvleetueeffeehueejgfeuteeftddt ieekgfekudehtdfgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 29 Jun 2022 03:10:57 -0400 (EDT) From: Thomas Monjalon To: "Chautru, Nicolas" Cc: "dev@dpdk.org" Subject: Re: [PATCH v2] baseband/turbo_sw: Remove flexran_sdk meson option Date: Wed, 29 Jun 2022 09:10:56 +0200 Message-ID: <3775822.kdYZ1jHi8b@thomas> In-Reply-To: References: <1656361758-229424-1-git-send-email-nicolas.chautru@intel.com> <3367351.otsE0voPBg@thomas> 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 29/06/2022 02:16, Chautru, Nicolas: > > From: Thomas Monjalon > > > > 27/06/2022 22:29, Nicolas Chautru: > > > Hi Thomas, > > > This is change you requested earlier this year. This is targeting 22.11. > > > > OK thanks. > > > > > Basically we no longer pass a specific option but rely on pkgconfig. > > > There is small change to generate the .pc files that Intel will make available > > by end of year. Still the related change in DPDK is available now. > > > > It means we depend on a future version of Flexran? > > Please could you document the minimum version? > > I expect the new version to be available in FlexRAN 22.11 (hence in November as well). Is that a concern? One concern is to be able to test. I guess it won't be an issue for you. The other concern is to mandate the new version to the users. I am fine with that as long as it is documented.