patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Xueming Li <xuemingl@nvidia.com>
Cc: Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	 NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
	Kevin Traynor <ktraynor@redhat.com>,
	stable@dpdk.org
Subject: Re: [PATCH 1/2] 4-final-review: add new rte_version.h path
Date: Sun, 23 Apr 2023 11:48:55 +0100	[thread overview]
Message-ID: <CAMw=ZnQfxNr7K0d=arhbey_W0B_Bf-re_nOTckji_dU7a3QL1g@mail.gmail.com> (raw)
In-Reply-To: <20230423094751.8353-1-xuemingl@nvidia.com>

On Sun, 23 Apr 2023 at 10:48, Xueming Li <xuemingl@nvidia.com> wrote:
>
> Adds new path of rte_version.h
>
> Signed-off-by: Xueming Li <xuemingl@nvidia.com>
> ---
>  4-final-review | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/4-final-review b/4-final-review
> index 4aa4a75..9eab987 100755
> --- a/4-final-review
> +++ b/4-final-review
> @@ -8,6 +8,8 @@ if [ -r "$DPDK_DIR/lib/librte_eal/include/rte_version.h" ]; then
>         VERSION_HEADER="$DPDK_DIR/lib/librte_eal/include/rte_version.h"
>  elif [ -r "$DPDK_DIR/lib/librte_eal/common/include/rte_version.h" ]; then
>         VERSION_HEADER="$DPDK_DIR/lib/librte_eal/common/include/rte_version.h"
> +elif [ -r "$DPDK_DIR/lib/eal/include/rte_version.h" ]; then
> +       VERSION_HEADER="$DPDK_DIR/lib/eal/include/rte_version.h"
>  else
>         echo "Cannot find rte_version.h"
>         exit 1

Acked-by: Luca Boccassi <bluca@debian.org>

      parent reply	other threads:[~2023-04-23 10:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-23  9:47 Xueming Li
2023-04-23  9:47 ` [PATCH 2/2] validation-contacts: fix email address Xueming Li
2023-04-23 10:49   ` Luca Boccassi
2023-04-23 10:48 ` Luca Boccassi [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='CAMw=ZnQfxNr7K0d=arhbey_W0B_Bf-re_nOTckji_dU7a3QL1g@mail.gmail.com' \
    --to=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=ktraynor@redhat.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=xuemingl@nvidia.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).