From: David Marchand <david.marchand@redhat.com>
To: Slava Ovsiienko <viacheslavo@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
Matan Azrad <matan@nvidia.com>
Subject: Re: [PATCH] net/mlx5: fix build with GCC 12 and ASan
Date: Wed, 15 Mar 2023 11:05:10 +0100 [thread overview]
Message-ID: <CAJFAV8y3D8jAENqTHot2=yxzqTJ1rmFPJXFaaAVrtU4s=nBt1g@mail.gmail.com> (raw)
In-Reply-To: <DM6PR12MB37536CF3A3B2952A45EFC5DDDFBE9@DM6PR12MB3753.namprd12.prod.outlook.com>
On Tue, Mar 14, 2023 at 2:00 PM Slava Ovsiienko <viacheslavo@nvidia.com> wrote:
>
> Hi, David
>
> Thank you for the fix.
> I see the quite similar strncpy() usage in mlx5_xstats_get_names() routine.
> Does compiler complain about?
Strangely.. no.
But we could switch to strlcpy too.
What is your preferrence?
--
David Marchand
next prev parent reply other threads:[~2023-03-15 10:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 9:03 David Marchand
2023-03-14 9:02 ` David Marchand
2023-03-14 13:00 ` Slava Ovsiienko
2023-03-15 10:05 ` David Marchand [this message]
2023-03-15 12:08 ` Slava Ovsiienko
2023-03-22 17:06 ` [PATCH v2] " David Marchand
2023-03-23 11:01 ` Raslan Darawsheh
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='CAJFAV8y3D8jAENqTHot2=yxzqTJ1rmFPJXFaaAVrtU4s=nBt1g@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@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).