patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Loftus, Ciara" <ciara.loftus@intel.com>
To: David Marchand <david.marchand@redhat.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	"Zhang, Qi Z" <qi.z.zhang@intel.com>,
	 Xiaolong Ye <xiaolong.ye@intel.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	Luca Boccassi <bluca@debian.org>,
	"Laatz, Kevin" <kevin.laatz@intel.com>
Subject: RE: [PATCH] net/af_xdp: add missing trailing newline in logs
Date: Thu, 17 Feb 2022 13:34:38 +0000	[thread overview]
Message-ID: <PH0PR11MB479146A0F1E3B508F7D8B3A78E369@PH0PR11MB4791.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220217130614.23255-1-david.marchand@redhat.com>

> Subject: [PATCH] net/af_xdp: add missing trailing newline in logs
> 
> Caught while trying --in-memory mode, some log messages in this driver
> are not terminated with a newline:
> rte_pmd_af_xdp_probe(): net_af_xdp: Failed to register multi-process IPC
> callback: Operation not supportedvdev_probe(): failed to initialize
> net_af_xdp device
> 
> Other locations in this driver had the same issue, fix all at once.
> 
> Fixes: f1debd77efaf ("net/af_xdp: introduce AF_XDP PMD")
> Fixes: d8a210774e1d ("net/af_xdp: support unaligned umem chunks")
> Fixes: 9876cf8316b3 ("net/af_xdp: re-enable secondary process support")
> Cc: stable@dpdk.org
> 
> Signed-off-by: David Marchand <david.marchand@redhat.com>

Thanks David, LGTM.

Acked-by: Ciara Loftus <ciara.loftus@intel.com>

> ---
>  drivers/net/af_xdp/rte_eth_af_xdp.c | 12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/net/af_xdp/rte_eth_af_xdp.c
> b/drivers/net/af_xdp/rte_eth_af_xdp.c
> index 6ac710c6bd..8bdc2920cf 100644
> --- a/drivers/net/af_xdp/rte_eth_af_xdp.c
> +++ b/drivers/net/af_xdp/rte_eth_af_xdp.c
> @@ -1071,7 +1071,7 @@ xsk_umem_info *xdp_umem_configure(struct
> pmd_internals *internals,
>  		umem = rte_zmalloc_socket("umem", sizeof(*umem), 0,
>  					  rte_socket_id());
>  		if (umem == NULL) {
> -			AF_XDP_LOG(ERR, "Failed to allocate umem info");
> +			AF_XDP_LOG(ERR, "Failed to allocate umem info\n");
>  			return NULL;
>  		}
> 
> @@ -1084,7 +1084,7 @@ xsk_umem_info *xdp_umem_configure(struct
> pmd_internals *internals,
>  		ret = xsk_umem__create(&umem->umem, base_addr,
> umem_size,
>  				&rxq->fq, &rxq->cq, &usr_config);
>  		if (ret) {
> -			AF_XDP_LOG(ERR, "Failed to create umem");
> +			AF_XDP_LOG(ERR, "Failed to create umem\n");
>  			goto err;
>  		}
>  		umem->buffer = base_addr;
> @@ -1124,7 +1124,7 @@ xsk_umem_info *xdp_umem_configure(struct
> pmd_internals *internals,
> 
>  	umem = rte_zmalloc_socket("umem", sizeof(*umem), 0,
> rte_socket_id());
>  	if (umem == NULL) {
> -		AF_XDP_LOG(ERR, "Failed to allocate umem info");
> +		AF_XDP_LOG(ERR, "Failed to allocate umem info\n");
>  		return NULL;
>  	}
> 
> @@ -1160,7 +1160,7 @@ xsk_umem_info *xdp_umem_configure(struct
> pmd_internals *internals,
>  			       &usr_config);
> 
>  	if (ret) {
> -		AF_XDP_LOG(ERR, "Failed to create umem");
> +		AF_XDP_LOG(ERR, "Failed to create umem\n");
>  		goto err;
>  	}
>  	umem->mz = mz;
> @@ -1847,7 +1847,7 @@ afxdp_mp_request_fds(const char *name, struct
> rte_eth_dev *dev)
>  	AF_XDP_LOG(DEBUG, "Sending multi-process IPC request for %s\n",
> name);
>  	ret = rte_mp_request_sync(&request, &replies, &timeout);
>  	if (ret < 0 || replies.nb_received != 1) {
> -		AF_XDP_LOG(ERR, "Failed to request fds from primary: %d",
> +		AF_XDP_LOG(ERR, "Failed to request fds from primary:
> %d\n",
>  			   rte_errno);
>  		return -1;
>  	}
> @@ -1996,7 +1996,7 @@ rte_pmd_af_xdp_probe(struct rte_vdev_device
> *dev)
>  	if (!afxdp_dev_count) {
>  		ret = rte_mp_action_register(ETH_AF_XDP_MP_KEY,
> afxdp_mp_send_fds);
>  		if (ret < 0) {
> -			AF_XDP_LOG(ERR, "%s: Failed to register multi-
> process IPC callback: %s",
> +			AF_XDP_LOG(ERR, "%s: Failed to register multi-
> process IPC callback: %s\n",
>  				   name, strerror(rte_errno));
>  			return -1;
>  		}
> --
> 2.23.0


  reply	other threads:[~2022-02-17 13:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17 13:06 David Marchand
2022-02-17 13:34 ` Loftus, Ciara [this message]
2022-02-17 17:55   ` Ferruh Yigit

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=PH0PR11MB479146A0F1E3B508F7D8B3A78E369@PH0PR11MB4791.namprd11.prod.outlook.com \
    --to=ciara.loftus@intel.com \
    --cc=bluca@debian.org \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=kevin.laatz@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=xiaolong.ye@intel.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).