DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>, dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com
Subject: Re: [PATCH 0/2] reduce the length of PCI name
Date: Wed, 21 Jun 2023 18:28:18 +0100	[thread overview]
Message-ID: <bf0d7fdb-dedd-7815-f2ee-f7aca734f5bd@amd.com> (raw)
In-Reply-To: <20230615065131.1267711-1-chaoyong.he@corigine.com>

On 6/15/2023 7:51 AM, Chaoyong He wrote:
> Use the complete PCI name as the part of representor port name cause the
> app crash, because the name is too long.
> 
> Fix this by reduce the length, using only the parts after the first ':'.
> 
> To keep unification, also use the same approach for the name of hash
> parameters.
> 
> Long Wu (2):
>   net/nfp: fix representor name too long
>   net/nfp: reduce the length of PCI name
>

Series applied to dpdk-next-net/main, thanks.


      parent reply	other threads:[~2023-06-21 17:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15  6:51 Chaoyong He
2023-06-15  6:51 ` [PATCH 1/2] net/nfp: fix representor name too long Chaoyong He
2023-06-15  6:51 ` [PATCH 2/2] net/nfp: reduce the length of PCI name Chaoyong He
2023-06-21 17:28 ` 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=bf0d7fdb-dedd-7815-f2ee-f7aca734f5bd@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=chaoyong.he@corigine.com \
    --cc=dev@dpdk.org \
    --cc=niklas.soderlund@corigine.com \
    --cc=oss-drivers@corigine.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).