DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xueming(Steven) Li" <xuemingl@nvidia.com>
To: "dev@dpdk.org" <dev@dpdk.org>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>
Cc: Parav Pandit <parav@nvidia.com>,
	"andrew.rybchenko@oktetlabs.ru" <andrew.rybchenko@oktetlabs.ru>,
	"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Subject: Re: [PATCH] bus/auxiliary: fix device iteration
Date: Mon, 22 Nov 2021 09:43:00 +0000	[thread overview]
Message-ID: <6ff4ac2f489b1f34c6be9bcb609e7cf64be287a1.camel@nvidia.com> (raw)
In-Reply-To: <20211122092543.29731-1-david.marchand@redhat.com>

On Mon, 2021-11-22 at 10:25 +0100, David Marchand wrote:
> rte_kvargs_parse() expects a NULL terminated keys array.
> 
> Fixes: 1afce3086cf4 ("bus/auxiliary: introduce auxiliary bus")
> 
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
>  drivers/bus/auxiliary/auxiliary_params.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/bus/auxiliary/auxiliary_params.c b/drivers/bus/auxiliary/auxiliary_params.c
> index a9c7853ed1..d115e11d32 100644
> --- a/drivers/bus/auxiliary/auxiliary_params.c
> +++ b/drivers/bus/auxiliary/auxiliary_params.c
> @@ -18,6 +18,7 @@ enum auxiliary_params {
>  
>  static const char * const auxiliary_params_keys[] = {
>  	[RTE_AUXILIARY_PARAM_NAME] = "name",
> +	NULL,
>  };
>  
>  static int

Nice catch, thanks!

Acked by: Xueming Li <xuemingl@nvidia.com>


  reply	other threads:[~2021-11-22  9:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22  9:25 David Marchand
2021-11-22  9:43 ` Xueming(Steven) Li [this message]
2021-11-24 13:19   ` 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=6ff4ac2f489b1f34c6be9bcb609e7cf64be287a1.camel@nvidia.com \
    --to=xuemingl@nvidia.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=parav@nvidia.com \
    --cc=thomas@monjalon.net \
    /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).