patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Loftus, Ciara" <ciara.loftus@intel.com>,
	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>,
	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 17:55:00 +0000	[thread overview]
Message-ID: <c66c28d3-4b64-35a9-4ec1-b2f24cde5579@intel.com> (raw)
In-Reply-To: <PH0PR11MB479146A0F1E3B508F7D8B3A78E369@PH0PR11MB4791.namprd11.prod.outlook.com>

On 2/17/2022 1:34 PM, Loftus, Ciara wrote:
>> 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>
> 

Applied to dpdk-next-net/main, thanks.


      reply	other threads:[~2022-02-17 17:55 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
2022-02-17 17:55   ` Ferruh Yigit [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=c66c28d3-4b64-35a9-4ec1-b2f24cde5579@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bluca@debian.org \
    --cc=ciara.loftus@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --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).