patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Heinrich Kuhn <heinrich.kuhn@netronome.com>, dev@dpdk.org
Cc: stable@dpdk.org, Simon Horman <simon.horman@netronome.com>
Subject: Re: [dpdk-stable] [dpdk-dev][PATCH] net/nfp: expand dev_infos_get callback function
Date: Tue, 15 Sep 2020 12:49:43 +0100	[thread overview]
Message-ID: <a844a2ef-f5a3-dbe2-76b3-2d7f368f6aa9@intel.com> (raw)
In-Reply-To: <20200902115227.15802-1-heinrich.kuhn@netronome.com>

On 9/2/2020 12:52 PM, Heinrich Kuhn wrote:
> Report Rx and Tx descriptor related limitations in the nfp dev_info_get
> callback function. This commit also adds NFP_ALIGN_RING_DESC to replace
> a static integer value used during rx/tx queue setups to validate
> descriptor alignment.
> 
> Cc: stable@dpdk.org
> 
> Signed-off-by: Heinrich Kuhn <heinrich.kuhn@netronome.com>
> Signed-off-by: Simon Horman <simon.horman@netronome.com>

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


      reply	other threads:[~2020-09-15 11:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02 11:52 Heinrich Kuhn
2020-09-15 11:49 ` 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=a844a2ef-f5a3-dbe2-76b3-2d7f368f6aa9@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=heinrich.kuhn@netronome.com \
    --cc=simon.horman@netronome.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).