From: David Marchand <david.marchand@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [PATCH 0/6] Coverity related fixes
Date: Wed, 6 Mar 2024 21:08:48 +0100 [thread overview]
Message-ID: <CAJFAV8xLKqX5sL1U72pL=Rgn_ZSRuw-OQGQHq-UF+CJT0-4LJA@mail.gmail.com> (raw)
In-Reply-To: <20240301175842.159967-1-stephen@networkplumber.org>
On Fri, Mar 1, 2024 at 6:59 PM Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
> Some small stuff that can be picked up after 24.03
>
> Stephen Hemminger (6):
> test/bpf: make sure mbuf is initialized
> net/tap: log if netlink ext ack not possible
> examples/l2fwd-keepalive: use rte_drand_max
> net/qede: replace use of rand()
> pipeline: replace use of rand()
> baseband/fpga_5gnr: don't use rand()
>
> app/test/test_bpf.c | 1 +
> drivers/baseband/fpga_5gnr_fec/rte_fpga_5gnr_fec.c | 3 ++-
> drivers/net/qede/qede_ethdev.c | 4 ++--
> drivers/net/tap/tap_netlink.c | 3 ++-
> examples/l2fwd-keepalive/main.c | 3 ++-
> lib/pipeline/rte_swx_ipsec.c | 3 ++-
> 6 files changed, 11 insertions(+), 6 deletions(-)
Series applied, thanks.
--
David Marchand
prev parent reply other threads:[~2024-03-06 20:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 17:57 Stephen Hemminger
2024-03-01 17:57 ` [PATCH 1/6] test/bpf: make sure mbuf is initialized Stephen Hemminger
2024-03-01 18:09 ` Tyler Retzlaff
2024-03-01 17:57 ` [PATCH 2/6] net/tap: log if netlink ext ack not possible Stephen Hemminger
2024-03-01 17:57 ` [PATCH 3/6] examples/l2fwd-keepalive: use rte_drand_max Stephen Hemminger
2024-03-01 17:57 ` [PATCH 4/6] net/qede: replace use of rand() Stephen Hemminger
2024-03-01 18:10 ` Tyler Retzlaff
2024-03-01 17:57 ` [PATCH 5/6] pipeline: " Stephen Hemminger
2024-03-01 18:11 ` Tyler Retzlaff
2024-03-01 17:57 ` [PATCH 6/6] baseband/fpga_5gnr: don't use rand() Stephen Hemminger
2024-03-01 18:11 ` Tyler Retzlaff
2024-03-02 1:07 ` Chautru, Nicolas
2024-03-06 20:08 ` David Marchand [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='CAJFAV8xLKqX5sL1U72pL=Rgn_ZSRuw-OQGQHq-UF+CJT0-4LJA@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).