DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rasesh Mody <rmody@marvell.com>,
	dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>
Cc: GR-Everest-DPDK-Dev@marvell.com
Subject: Re: [dpdk-dev] [PATCH v2] doc: update qede PMD guide
Date: Mon, 25 Nov 2019 15:32:11 +0000	[thread overview]
Message-ID: <1eaeca56-e45e-8955-51b5-a0bd64038a48@intel.com> (raw)
In-Reply-To: <20191122233118.31999-1-rmody@marvell.com>

On 11/22/2019 11:31 PM, Rasesh Mody wrote:
>  - Add note for sharing an adapter between DPDK and Linux drivers.
>  - Update the firmware version in example.
>  - Add Config note for potential error due to lack of memzone desciptor
>    count.
> 
> Signed-off-by: Rasesh Mody <rmody@marvell.com>

Applied to dpdk-next-net/master, thanks.

      reply	other threads:[~2019-11-25 15:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-22  7:51 [dpdk-dev] [PATCH] " Rasesh Mody
2019-11-22 14:32 ` Ferruh Yigit
2019-11-22 19:42   ` [dpdk-dev] [EXT] " Rasesh Mody
2019-11-22 23:31 ` [dpdk-dev] [PATCH v2] " Rasesh Mody
2019-11-25 15:32   ` Ferruh Yigit [this message]

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=1eaeca56-e45e-8955-51b5-a0bd64038a48@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=GR-Everest-DPDK-Dev@marvell.com \
    --cc=dev@dpdk.org \
    --cc=rmody@marvell.com \
    --cc=thomas@monjalon.net \
    /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).