DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, "Thomas Monjalon" <thomas@monjalon.net>,
	"Morten Brørup" <mb@smartsharesystems.com>,
	"Ciara Power" <ciara.power@intel.com>,
	"Chengwen Feng" <fengchengwen@huawei.com>,
	"Kevin Laatz" <kevin.laatz@intel.com>,
	"Bruce Richardson" <bruce.richardson@intel.com>,
	"Elena Agostini" <eagostini@nvidia.com>,
	"Jerin Jacob" <jerinj@marvell.com>,
	"Kiran Kumar K" <kirankumark@marvell.com>,
	"Nithin Dabilpuram" <ndabilpuram@marvell.com>,
	"Zhirun Yan" <zhirun.yan@intel.com>,
	"Pavan Nikhilesh" <pbhagavatula@marvell.com>,
	"Maxime Coquelin" <maxime.coquelin@redhat.com>,
	"Chenbo Xia" <chenbox@nvidia.com>,
	"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>
Subject: Re: [PATCH v2] lib: remove duplicate prefix in logs
Date: Thu, 1 Feb 2024 09:53:16 +0100	[thread overview]
Message-ID: <CAJFAV8yx0oSbJcnpxSrE4QT64ooNiKrp4cn_UbvRU+i8YYz7aQ@mail.gmail.com> (raw)
In-Reply-To: <20240125125550.1100670-1-david.marchand@redhat.com>

On Thu, Jan 25, 2024 at 1:56 PM David Marchand
<david.marchand@redhat.com> wrote:
>
> RTE_LOG() macros prefixe the log messages based on the logtype.
> This results in logs like:
>
> TMTY: TELEMETRY: Attempting socket bind to path '/run/user/...'
> TMTY: TELEMETRY: Socket creation and binding ok
> TMTY: TELEMETRY: Telemetry initialized ok
>
> Remove redundancy in some libraries following their conversion to
> RTE_LOG/RTE_LOG_LINE.
>
> Note: for consistency, dmadev logs are now prefixed with "DMADEV: "
> instead of a too generic "dma: ".
>
> Fixes: 97433132c2ed ("lib: use per line logging in helpers")
> Fixes: 0e21c7c07d62 ("lib: replace logging helpers")
>
> Reported-by: Thomas Monjalon <thomas@monjalon.net>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> Acked-by: Morten Brørup <mb@smartsharesystems.com>
> Acked-by: Ciara Power <ciara.power@intel.com>
> Reviewed-by: Chengwen Feng <fengchengwen@huawei.com>

Applied, thanks.


-- 
David Marchand


      reply	other threads:[~2024-02-01  8:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24 12:04 [PATCH] " David Marchand
2024-01-24 12:17 ` Morten Brørup
2024-01-25  8:13   ` David Marchand
2024-01-25  8:53     ` Morten Brørup
2024-01-24 13:26 ` Bruce Richardson
2024-01-24 13:28   ` Bruce Richardson
2024-01-24 14:39 ` Power, Ciara
2024-01-25  3:06 ` fengchengwen
2024-01-25 12:55 ` [PATCH v2] " David Marchand
2024-02-01  8:53   ` David Marchand [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=CAJFAV8yx0oSbJcnpxSrE4QT64ooNiKrp4cn_UbvRU+i8YYz7aQ@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=bruce.richardson@intel.com \
    --cc=chenbox@nvidia.com \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=eagostini@nvidia.com \
    --cc=fengchengwen@huawei.com \
    --cc=jerinj@marvell.com \
    --cc=kevin.laatz@intel.com \
    --cc=kirankumark@marvell.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=mb@smartsharesystems.com \
    --cc=ndabilpuram@marvell.com \
    --cc=pbhagavatula@marvell.com \
    --cc=thomas@monjalon.net \
    --cc=zhirun.yan@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).