From: Thomas Monjalon <thomas@monjalon.net>
To: Shreyansh Jain <shreyansh.jain@nxp.com>
Cc: dev@dpdk.org, "ferruh.yigit@intel.com" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/3] Update FSLMC bus firmware
Date: Thu, 04 Apr 2019 23:08:48 +0200 [thread overview]
Message-ID: <2002716.sjzEUOpA7y@xps> (raw)
Message-ID: <20190404210848.JS-qpAjwdvPuV0iZuG361IEI8yATzuXxBb4QVBM_en0@z> (raw)
In-Reply-To: <20190404072335.24555-1-shreyansh.jain@nxp.com>
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
next prev parent reply other threads:[~2019-04-04 21:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 14:23 [dpdk-dev] [PATCH " Shreyansh Jain
2019-04-03 14:23 ` Shreyansh Jain
2019-04-03 14:23 ` [dpdk-dev] [PATCH 1/3] bus/fslmc: cleanup unused firmware code Shreyansh Jain
2019-04-03 14:23 ` Shreyansh Jain
2019-04-03 14:23 ` [dpdk-dev] [PATCH 2/3] drivers: update MC firmware version for FSLMC bus Shreyansh Jain
2019-04-03 14:23 ` Shreyansh Jain
2019-04-03 14:23 ` [dpdk-dev] [PATCH 3/3] doc: bump SDK support version for dpaa2 Shreyansh Jain
2019-04-03 14:23 ` Shreyansh Jain
2019-04-04 7:23 ` [dpdk-dev] [PATCH v2 0/3] Update FSLMC bus firmware Shreyansh Jain
2019-04-04 7:23 ` Shreyansh Jain
2019-04-04 7:23 ` [dpdk-dev] [PATCH v2 1/3] bus/fslmc: cleanup unused firmware code Shreyansh Jain
2019-04-04 7:23 ` Shreyansh Jain
2019-04-04 21:29 ` Ferruh Yigit
2019-04-04 21:29 ` Ferruh Yigit
2019-04-04 21:43 ` Thomas Monjalon
2019-04-04 21:43 ` Thomas Monjalon
2019-04-05 11:19 ` Shreyansh Jain
2019-04-05 11:19 ` Shreyansh Jain
2019-04-05 11:37 ` Ferruh Yigit
2019-04-05 11:37 ` Ferruh Yigit
2019-04-05 11:38 ` Shreyansh Jain
2019-04-05 11:38 ` Shreyansh Jain
2019-04-05 12:35 ` Thomas Monjalon
2019-04-05 12:35 ` Thomas Monjalon
2019-04-05 12:58 ` Shreyansh Jain
2019-04-05 12:58 ` Shreyansh Jain
2019-04-04 7:23 ` [dpdk-dev] [PATCH v2 2/3] drivers: update MC firmware version for FSLMC bus Shreyansh Jain
2019-04-04 7:23 ` Shreyansh Jain
2019-04-04 7:23 ` [dpdk-dev] [PATCH v2 3/3] doc: bump SDK support version for dpaa2 Shreyansh Jain
2019-04-04 7:23 ` Shreyansh Jain
2019-04-04 21:08 ` Thomas Monjalon [this message]
2019-04-04 21:08 ` [dpdk-dev] [PATCH v2 0/3] Update FSLMC bus firmware Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2002716.sjzEUOpA7y@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=shreyansh.jain@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).