DPDK website maintenance
 help / color / mirror / Atom feed
From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "web@dpdk.org" <web@dpdk.org>, Gagandeep Singh <G.Singh@nxp.com>
Subject: Re: [dpdk-web] [PATCH v2] update NXP NICs and add newly supported device
Date: Thu, 22 Nov 2018 11:15:08 +0000	[thread overview]
Message-ID: <VI1PR04MB46888B10B2F7FB0C24D7ABFA90DB0@VI1PR04MB4688.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <6457013.azZNpyoqg0@xps>

Hi Thomas,

> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Thursday, November 22, 2018 4:05 PM
> To: Shreyansh Jain <shreyansh.jain@nxp.com>
> Cc: web@dpdk.org; Gagandeep Singh <G.Singh@nxp.com>
> Subject: Re: [dpdk-web] [PATCH v2] update NXP NICs and add newly
> supported device
> 
> 22/11/2018 11:32, Shreyansh Jain:

[...]


> 
> Please could you check my patches in this area?
> If you agree with my changes, please rebase on top (need to add enetc
> in description).

I am assuming you are talking about [1]
When do you plan to merge your patches?
Once you do that, I can place my patch over that for ENETC (and changes to existing device list).

[1] https://mails.dpdk.org/archives/web/2018-November/000942.html

  reply	other threads:[~2018-11-22 11:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-22 10:32 Shreyansh Jain
2018-11-22 10:34 ` Thomas Monjalon
2018-11-22 11:15   ` Shreyansh Jain [this message]
2018-11-22 11:39     ` Thomas Monjalon
2018-11-22 12:29       ` Shreyansh Jain
2018-11-22 13:58         ` Thomas Monjalon
2018-11-23  8:53 ` [dpdk-web] [PATCH v3] " Shreyansh Jain
2018-11-23  9:50   ` 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=VI1PR04MB46888B10B2F7FB0C24D7ABFA90DB0@VI1PR04MB4688.eurprd04.prod.outlook.com \
    --to=shreyansh.jain@nxp.com \
    --cc=G.Singh@nxp.com \
    --cc=thomas@monjalon.net \
    --cc=web@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).