From: David Marchand <david.marchand@redhat.com>
To: jerinj@marvell.com
Cc: Srikanth Yalavarthi <syalavarthi@marvell.com>,
Liron Himi <lironh@marvell.com>,
dev@dpdk.org, thomas@monjalon.net
Subject: Re: [dpdk-dev] [PATCH] drivers: fix build issues with redundant newline changes
Date: Mon, 7 Oct 2024 10:40:20 +0200 [thread overview]
Message-ID: <CAJFAV8xWg736QObUuzygE7NM7u-28dQJ7pUAUXrRE2ekqcb9Xw@mail.gmail.com> (raw)
In-Reply-To: <20241007081301.2999359-1-jerinj@marvell.com>
Hello Jerin,
On Mon, Oct 7, 2024 at 10:13 AM <jerinj@marvell.com> wrote:
>
> From: Jerin Jacob <jerinj@marvell.com>
>
> Certain section of the code in net/mvpp2 and ml/cnxk is enabled only
> when all depended library dependences where meet.
> Fixing those build errors.
Sorry for missing those.
Too bad there is no CI with such libraries installed.
>
> Fixes: e99981af3463 ("drivers: replace logging helpers")
I fixed other similar issues for ml/cnxk fixes in commit f665790a5dba
("drivers: remove redundant newline from logs").
net/mvpp2 was touched only with 2b843cac232e ("drivers: use per line
logging in helpers").
But the issues were present regardless of the changes in the logging macro.
In the end, I would rather flag this whole patch as:
Fixes: f665790a5dba ("drivers: remove redundant newline from logs").
>
> Signed-off-by: Jerin Jacob <jerinj@marvell.com>
Double checking manually, I think we are missing another small fix:
$ git diff
diff --git a/drivers/net/mvpp2/mrvl_qos.c b/drivers/net/mvpp2/mrvl_qos.c
index 3e98cce099..e298da2724 100644
--- a/drivers/net/mvpp2/mrvl_qos.c
+++ b/drivers/net/mvpp2/mrvl_qos.c
@@ -972,7 +972,7 @@ setup_policer(struct mrvl_priv *priv, struct
pp2_cls_plcr_params *params)
*
* Lets use 0th then.
*/
- sprintf(match, "policer-%d:%d\n", priv->pp_id, 0);
+ sprintf(match, "policer-%d:%d", priv->pp_id, 0);
params->match = match;
ret = pp2_cls_plcr_init(params, &priv->default_policer);
--
David Marchand
next prev parent reply other threads:[~2024-10-07 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 8:13 jerinj
2024-10-07 8:40 ` David Marchand [this message]
2024-10-07 12:41 ` [dpdk-dev] [PATCH v2] " jerinj
2024-10-08 6:55 ` 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=CAJFAV8xWg736QObUuzygE7NM7u-28dQJ7pUAUXrRE2ekqcb9Xw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=lironh@marvell.com \
--cc=syalavarthi@marvell.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).