patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: David Marchand <david.marchand@redhat.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 12:08:30 +0000	[thread overview]
Message-ID: <DM6PR12MB375363BAEA2B2ABE0871B3F2DFBF9@DM6PR12MB3753.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8y3D8jAENqTHot2=yxzqTJ1rmFPJXFaaAVrtU4s=nBt1g@mail.gmail.com>

Hi, 

I would prefer to fix both.

With best regards,
Slava

> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: среда, 15 марта 2023 г. 12:05
> To: Slava Ovsiienko <viacheslavo@nvidia.com>
> Cc: dev@dpdk.org; stable@dpdk.org; Matan Azrad <matan@nvidia.com>
> Subject: Re: [PATCH] net/mlx5: fix build with GCC 12 and ASan
> 
> 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


  reply	other threads:[~2023-03-15 12:08 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
2023-03-15 12:08     ` Slava Ovsiienko [this message]
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=DM6PR12MB375363BAEA2B2ABE0871B3F2DFBF9@DM6PR12MB3753.namprd12.prod.outlook.com \
    --to=viacheslavo@nvidia.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=stable@dpdk.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).