From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: David Marchand <david.marchand@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
Timothy Redaelli <tredaelli@redhat.com>
Subject: Re: [dpdk-stable] [PATCH] examples/pipeline: fix VXLAN script permission
Date: Fri, 22 Jan 2021 12:19:07 +0000 [thread overview]
Message-ID: <CY4PR11MB1702B4984F1047267AD91C1EEBA00@CY4PR11MB1702.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210122093037.21988-1-david.marchand@redhat.com>
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Friday, January 22, 2021 9:31 AM
> To: dev@dpdk.org
> Cc: stable@dpdk.org; Timothy Redaelli <tredaelli@redhat.com>; Dumitrescu,
> Cristian <cristian.dumitrescu@intel.com>
> Subject: [PATCH] examples/pipeline: fix VXLAN script permission
>
> This python script provides a shebang that only makes sense if the
> script has the executable bit set.
>
> Fixes: fde7a772701a ("examples/pipeline: add VXLAN encapsulation
> example")
> Cc: stable@dpdk.org
>
> Reported-by: Timothy Redaelli <tredaelli@redhat.com>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
> examples/pipeline/examples/vxlan_table.py | 0
> 1 file changed, 0 insertions(+), 0 deletions(-)
> mode change 100644 => 100755
> examples/pipeline/examples/vxlan_table.py
>
> diff --git a/examples/pipeline/examples/vxlan_table.py
> b/examples/pipeline/examples/vxlan_table.py
> old mode 100644
> new mode 100755
> --
> 2.23.0
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
next prev parent reply other threads:[~2021-01-22 12:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 9:30 David Marchand
2021-01-22 12:19 ` Dumitrescu, Cristian [this message]
2021-01-25 9:23 ` David Marchand
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=CY4PR11MB1702B4984F1047267AD91C1EEBA00@CY4PR11MB1702.namprd11.prod.outlook.com \
--to=cristian.dumitrescu@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=tredaelli@redhat.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).