From: Thomas Monjalon <thomas@monjalon.net>
To: Gagandeep Singh <G.Singh@nxp.com>
Cc: Pankaj Chauhan <pankaj.chauhan@nxp.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
ferruh.yigit@intel.com
Subject: Re: [dpdk-stable] [PATCH v2 2/2] net/enetc: fix big endian build
Date: Wed, 10 Apr 2019 13:43:51 +0200 [thread overview]
Message-ID: <5124836.70q5k3TLv3@xps> (raw)
In-Reply-To: <VE1PR04MB636506EE64618853FE8ADF70E12E0@VE1PR04MB6365.eurprd04.prod.outlook.com>
10/04/2019 13:27, Gagandeep Singh:
> I have sent a patch-set for ENETC driver having some changes in "enetc_refill_rx_ring".
> Is it ok for you if I can merge your changes with my patch-set and push them in v2?
>
> https://patches.dpdk.org/project/dpdk/list/?series=4173
Yes, no problem, at the condition it is integrated in 19.05-rc2.
next prev parent reply other threads:[~2019-04-10 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 11:27 Gagandeep Singh
2019-04-10 11:43 ` Thomas Monjalon [this message]
[not found] <20190409194904.6822-1-thomas@monjalon.net>
[not found] ` <20190409200636.2193-1-thomas@monjalon.net>
2019-04-09 20:06 ` 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=5124836.70q5k3TLv3@xps \
--to=thomas@monjalon.net \
--cc=G.Singh@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=pankaj.chauhan@nxp.com \
--cc=stable@dpdk.org \
/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).