All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Anoob Joseph <anoobj@marvell.com>
Cc: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
	dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>,
	Bruce Richardson <bruce.richardson@intel.com>,
	Jerin Jacob <jerinj@marvell.com>,
	dev@dpdk.org, sean.morrissey@intel.com
Subject: Re: [PATCH v2] rcu: fix build failure with debug dp log level
Date: Thu, 06 Oct 2022 12:40:24 +0200	[thread overview]
Message-ID: <832527881.0ifERbkFSE@thomas> (raw)
In-Reply-To: <20220929102714.550-1-anoobj@marvell.com>

29/09/2022 12:27, Anoob Joseph:
> Build fails if RTE_LOG_DP_LEVEL is set to RTE_LOG_DEBUG. Fix the
> same by including the required header.
> 
> ../lib/rcu/rte_rcu_qsbr.h:678:40: error: expected ‘)’ before ‘PRIu64’
>   678 |    "%s: status: least acked token = %" PRIu64,
>       |                                        ^~~~~~
> 
> Fixes: 30a1de105a5f ("lib: remove unneeded header includes")
> Cc: sean.morrissey@intel.com
> 
> Signed-off-by: Anoob Joseph <anoobj@marvell.com>

Applied, thanks.

Would be good to avoid the tool doing the same mistake again.




      reply	other threads:[~2022-10-06 10:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29 16:51 [PATCH] rcu: fix build failure with debug dp log level Anoob Joseph
2022-08-29 16:55 ` Honnappa Nagarahalli
2022-08-30  8:38   ` Morrissey, Sean
2022-08-30 13:17     ` Honnappa Nagarahalli
2022-09-28 22:04       ` Honnappa Nagarahalli
2022-09-28 22:21 ` Stephen Hemminger
2022-09-29  3:25   ` [EXT] " Anoob Joseph
2022-09-29  8:27     ` Bruce Richardson
2022-09-29 10:27 ` [PATCH v2] " Anoob Joseph
2022-10-06 10:40   ` Thomas Monjalon [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=832527881.0ifERbkFSE@thomas \
    --to=thomas@monjalon.net \
    --cc=anoobj@marvell.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=jerinj@marvell.com \
    --cc=sean.morrissey@intel.com \
    --cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.