From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 1A8301B399 for ; Thu, 4 Apr 2019 23:08:51 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 972B721CB9; Thu, 4 Apr 2019 17:08:50 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 04 Apr 2019 17:08:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=Y0wXqNn6jeJ5mCDuPg6cgGALUwW6uk3MyTzEnLhGQcE=; b=nr87/t+xmkb8 p/yiuvZtKRI0DEjEitkVbeS9PEPmxkTs92gW4w0ayqic0R6e+70I1YqZZNstkguX rIorckDirwc5cGzyu4wV9Be3srQniePTO7vKoOfCGHEi9Ru5s0H7n2a3rIcf1/MT 2oq1KV5lBRK0uhzNgVNQDXK6yMYr5iI= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=Y0wXqNn6jeJ5mCDuPg6cgGALUwW6uk3MyTzEnLhGQ cE=; b=aasJNuqNvliW6CLb7zRrdq8YL/el8y/A9OuLaI5K/HNXyKlkCEuaIObSK sbcEZqHWtvvhsdGOy74upDMaHqLSC6PeGZ3C7IEJ56osNMIdY8mSOw2F0DbTqWYv dubGLXB5hIW+Ughutf2RyOxeiijxtm2A/VQ1AbmgmNY/hNE0hmbOw7ilbq2AiEr0 KM0ZOO06cchrj71yEVn5/KKVjQU35ypvnytjRsOyPacikDrsK5nIAHmUdbXPxlgk sc8L1MygOFS29apA+dTvsy/NMV0jl/X8p8MWfukMImUBK2wEVlWNYcXNf8ZFfiKd mkfhezqc9vcq0jyc/ObL/Ziw7s+9w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrtdehgdduheeiucdltddurdeguddtrddttd dmucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfv pdfurfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpih gvnhhtshculddquddttddmnecujfgurhephffvufffkfgjfhgggfgtsehtufertddttddv necuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjh grlhhonhdrnhgvtheqnecukfhppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghm pehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhush htvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 54D0310310; Thu, 4 Apr 2019 17:08:49 -0400 (EDT) From: Thomas Monjalon To: Shreyansh Jain Cc: dev@dpdk.org, "ferruh.yigit@intel.com" Date: Thu, 04 Apr 2019 23:08:48 +0200 Message-ID: <2002716.sjzEUOpA7y@xps> In-Reply-To: <20190404072335.24555-1-shreyansh.jain@nxp.com> References: <20190403142357.17700-1-shreyansh.jain@nxp.com> <20190404072335.24555-1-shreyansh.jain@nxp.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2 0/3] Update FSLMC bus firmware X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Apr 2019 21:08:51 -0000 04/04/2019 09:23, Shreyansh Jain: > Based on net-next: 69f805ac18abe > > All the patches are strictly within DPAA2/FSLMC driver area. > > MC firmware is the core component of FSLMC bus which enables > all the dpaa2 devices (eth, crypto etc). > With recent release of NXP's layerscape SDK, the MC firmware > has been bumped up. These patches updates only necessary > changes so as to maintain version compatibility. > > v1->v2: > - In last patch (patch 2), one of a recent fix (e94be227b7) > was overwritten. Restoring that change. > > Shreyansh Jain (3): > bus/fslmc: cleanup unused firmware code > drivers: update MC firmware version for FSLMC bus > doc: bump SDK support version for dpaa2 Applied, thanks From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 55ADAA0679 for ; Thu, 4 Apr 2019 23:08:54 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id E67871B3B9; Thu, 4 Apr 2019 23:08:52 +0200 (CEST) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 1A8301B399 for ; Thu, 4 Apr 2019 23:08:51 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 972B721CB9; Thu, 4 Apr 2019 17:08:50 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 04 Apr 2019 17:08:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=Y0wXqNn6jeJ5mCDuPg6cgGALUwW6uk3MyTzEnLhGQcE=; b=nr87/t+xmkb8 p/yiuvZtKRI0DEjEitkVbeS9PEPmxkTs92gW4w0ayqic0R6e+70I1YqZZNstkguX rIorckDirwc5cGzyu4wV9Be3srQniePTO7vKoOfCGHEi9Ru5s0H7n2a3rIcf1/MT 2oq1KV5lBRK0uhzNgVNQDXK6yMYr5iI= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=Y0wXqNn6jeJ5mCDuPg6cgGALUwW6uk3MyTzEnLhGQ cE=; b=aasJNuqNvliW6CLb7zRrdq8YL/el8y/A9OuLaI5K/HNXyKlkCEuaIObSK sbcEZqHWtvvhsdGOy74upDMaHqLSC6PeGZ3C7IEJ56osNMIdY8mSOw2F0DbTqWYv dubGLXB5hIW+Ughutf2RyOxeiijxtm2A/VQ1AbmgmNY/hNE0hmbOw7ilbq2AiEr0 KM0ZOO06cchrj71yEVn5/KKVjQU35ypvnytjRsOyPacikDrsK5nIAHmUdbXPxlgk sc8L1MygOFS29apA+dTvsy/NMV0jl/X8p8MWfukMImUBK2wEVlWNYcXNf8ZFfiKd mkfhezqc9vcq0jyc/ObL/Ziw7s+9w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrtdehgdduheeiucdltddurdeguddtrddttd dmucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfv pdfurfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpih gvnhhtshculddquddttddmnecujfgurhephffvufffkfgjfhgggfgtsehtufertddttddv necuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjh grlhhonhdrnhgvtheqnecukfhppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghm pehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhush htvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 54D0310310; Thu, 4 Apr 2019 17:08:49 -0400 (EDT) From: Thomas Monjalon To: Shreyansh Jain Cc: dev@dpdk.org, "ferruh.yigit@intel.com" Date: Thu, 04 Apr 2019 23:08:48 +0200 Message-ID: <2002716.sjzEUOpA7y@xps> In-Reply-To: <20190404072335.24555-1-shreyansh.jain@nxp.com> References: <20190403142357.17700-1-shreyansh.jain@nxp.com> <20190404072335.24555-1-shreyansh.jain@nxp.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH v2 0/3] Update FSLMC bus firmware X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190404210848.JS-qpAjwdvPuV0iZuG361IEI8yATzuXxBb4QVBM_en0@z> 04/04/2019 09:23, Shreyansh Jain: > Based on net-next: 69f805ac18abe > > All the patches are strictly within DPAA2/FSLMC driver area. > > MC firmware is the core component of FSLMC bus which enables > all the dpaa2 devices (eth, crypto etc). > With recent release of NXP's layerscape SDK, the MC firmware > has been bumped up. These patches updates only necessary > changes so as to maintain version compatibility. > > v1->v2: > - In last patch (patch 2), one of a recent fix (e94be227b7) > was overwritten. Restoring that change. > > Shreyansh Jain (3): > bus/fslmc: cleanup unused firmware code > drivers: update MC firmware version for FSLMC bus > doc: bump SDK support version for dpaa2 Applied, thanks