DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Harry van Haaren <harry.van.haaren@intel.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
	ferruh.yigit@intel.com, liang.j.ma@intel.com,
	santosh.shukla@caviumnetworks.com,
	jerin.jacob@caviumnetworks.com, alejandro.lucero@netronome.com,
	allain.legacy@windriver.com, amr.mokhtar@intel.com,
	beilei.xing@intel.com, evgenys@amazon.com, gtzalik@amazon.com,
	harish.patil@cavium.com, hyonkim@cisco.com,
	jingjing.wu@intel.com, johndale@cisco.com,
	konstantin.ananyev@intel.com, maciej.czekaj@caviumnetworks.com,
	matt.peters@windriver.com, maxime.coquelin@redhat.com,
	mk@semihalf.com, mw@semihalf.com, qi.z.zhang@intel.com,
	rasesh.mody@cavium.com, shahed.shaikh@cavium.com,
	shijith.thotton@cavium.com, skhare@vmware.com,
	ssrinivasan@cavium.com, tiwei.bie@intel.com,
	wenzhuo.lu@intel.com, xiao.w.wang@intel.com,
	yliu@fridaylinux.org
Subject: Re: [dpdk-dev] [PATCH 00/18] dynamic logging naming scheme
Date: Wed, 31 Jan 2018 09:28:34 +0100	[thread overview]
Message-ID: <2371356.BLLSGZ6nlC@xps> (raw)
In-Reply-To: <20180126101441.GA17148@bricha3-MOBL3.ger.corp.intel.com>

26/01/2018 11:14, Bruce Richardson:
> On Thu, Jan 25, 2018 at 09:00:52AM +0000, Harry van Haaren wrote:
> > This patchset adds and documents a defined naming scheme
> > for logging. As the user selects logging topics of
> > interest, it is important for usability that the topics
> > are consistently named.
> > 
> > The first patch of this patchset documents the new naming
> > format, please review for clarity.
> > 
> > The other 17 patches bring the existing dynamic logging
> > in line with the newly documented naming scheme.
> > 
> > Sorry for the wide email, maintainers just review own patches :)
> > 
> > Regards, -Harry
> > 
> I think standardizing is a great idea so:
> 
> Series Acked-by: Bruce Richardson <bruce.richardson@intel.com>

Applied, thanks

      reply	other threads:[~2018-01-31  8:29 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25  9:00 Harry van Haaren
2018-01-25  9:00 ` [dpdk-dev] [PATCH 01/18] doc/contrib: document dynamic logging format Harry van Haaren
2018-01-25  9:23   ` Kovacevic, Marko
2018-01-25  9:00 ` [dpdk-dev] [PATCH 02/18] event/opdl: align dynamic log name with standard Harry van Haaren
2018-01-25 11:15   ` Liang, Ma
2018-01-25  9:00 ` [dpdk-dev] [PATCH 03/18] octeontx: align dynamic log names " Harry van Haaren
2018-01-25 11:29   ` Jerin Jacob
2018-01-25 14:19   ` santosh
2018-01-25  9:00 ` [dpdk-dev] [PATCH 04/18] bbdev: " Harry van Haaren
2018-01-25  9:00 ` [dpdk-dev] [PATCH 05/18] net/avf: " Harry van Haaren
2018-01-25  9:00 ` [dpdk-dev] [PATCH 06/18] net/avp: " Harry van Haaren
2018-01-25 12:05   ` Legacy, Allain
2018-01-25 17:05     ` Van Haaren, Harry
2018-01-25 17:46       ` Legacy, Allain
2018-01-25  9:00 ` [dpdk-dev] [PATCH 07/18] net/e1000: " Harry van Haaren
2018-01-25  9:01 ` [dpdk-dev] [PATCH 08/18] net/ena: " Harry van Haaren
2018-01-25  9:01 ` [dpdk-dev] [PATCH 09/18] net/enic: " Harry van Haaren
2018-01-25 16:30   ` Hyong Youb Kim
2018-01-25  9:01 ` [dpdk-dev] [PATCH 10/18] net/fm10k: " Harry van Haaren
2018-01-25  9:01 ` [dpdk-dev] [PATCH 11/18] net/i40e: " Harry van Haaren
2018-01-25  9:01 ` [dpdk-dev] [PATCH 12/18] net/ixgbe: " Harry van Haaren
2018-01-25  9:01 ` [dpdk-dev] [PATCH 13/18] net/liquidio: " Harry van Haaren
2018-01-27  5:21   ` Shijith Thotton
2018-01-25  9:01 ` [dpdk-dev] [PATCH 14/18] net/nfp: " Harry van Haaren
2018-01-26 11:00   ` Alejandro Lucero
2018-01-25  9:01 ` [dpdk-dev] [PATCH 15/18] net/qede: " Harry van Haaren
2018-01-25  9:01 ` [dpdk-dev] [PATCH 16/18] net/thunderx: " Harry van Haaren
2018-01-25 11:27   ` Jerin Jacob
2018-01-25  9:01 ` [dpdk-dev] [PATCH 17/18] net/virtio: " Harry van Haaren
2018-01-25 11:25   ` Maxime Coquelin
2018-01-25  9:01 ` [dpdk-dev] [PATCH 18/18] net/vmxnet3: " Harry van Haaren
2018-01-26 10:14 ` [dpdk-dev] [PATCH 00/18] dynamic logging naming scheme Bruce Richardson
2018-01-31  8:28   ` 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=2371356.BLLSGZ6nlC@xps \
    --to=thomas@monjalon.net \
    --cc=alejandro.lucero@netronome.com \
    --cc=allain.legacy@windriver.com \
    --cc=amr.mokhtar@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=evgenys@amazon.com \
    --cc=ferruh.yigit@intel.com \
    --cc=gtzalik@amazon.com \
    --cc=harish.patil@cavium.com \
    --cc=harry.van.haaren@intel.com \
    --cc=hyonkim@cisco.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=jingjing.wu@intel.com \
    --cc=johndale@cisco.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=liang.j.ma@intel.com \
    --cc=maciej.czekaj@caviumnetworks.com \
    --cc=matt.peters@windriver.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=mk@semihalf.com \
    --cc=mw@semihalf.com \
    --cc=qi.z.zhang@intel.com \
    --cc=rasesh.mody@cavium.com \
    --cc=santosh.shukla@caviumnetworks.com \
    --cc=shahed.shaikh@cavium.com \
    --cc=shijith.thotton@cavium.com \
    --cc=skhare@vmware.com \
    --cc=ssrinivasan@cavium.com \
    --cc=tiwei.bie@intel.com \
    --cc=wenzhuo.lu@intel.com \
    --cc=xiao.w.wang@intel.com \
    --cc=yliu@fridaylinux.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 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).