All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, "Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
	"Morten Brørup" <mb@smartsharesystems.com>,
	"David Marchand" <david.marchand@redhat.com>
Subject: Re: [PATCH v3] doc: add deprecation for restrictions in telemetry naming
Date: Fri, 15 Jul 2022 18:30:42 +0200	[thread overview]
Message-ID: <5738301.MhkbZ0Pkbq@thomas> (raw)
In-Reply-To: <20220712090952.205258-1-bruce.richardson@intel.com>

12/07/2022 11:09, Bruce Richardson:
> Following discussion on-list [1], we will look to limited the allowed
> characters in names for items in telemetry. This will simplify the
> escaping needed for json output, or any future output formats. The lists
> will initially be minimal, since expansion to allow more characters can
> be done without affecting compatibility, while reducing the set cannot.
> 
> [1] http://inbox.dpdk.org/dev/20220623164245.561371-1-bruce.richardson@intel.com/#r
> 
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>

    Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
    Acked-by: Morten Brørup <mb@smartsharesystems.com>
    Acked-by: Ciara Power <ciara.power@intel.com>
    Acked-by: David Marchand <david.marchand@redhat.com>

Applied, thanks.



      reply	other threads:[~2022-07-15 16:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07 13:39 [PATCH] doc: add deprecation for restrictions in telemetry naming Bruce Richardson
2022-07-07 15:16 ` Andrew Rybchenko
2022-07-07 22:06 ` Morten Brørup
2022-07-11 10:53   ` Bruce Richardson
2022-07-11 11:40     ` Morten Brørup
2022-07-11 10:43 ` Power, Ciara
2022-07-11 10:45 ` David Marchand
2022-07-12  9:04 ` [PATCH v2] " Bruce Richardson
2022-07-12  9:09 ` [PATCH v3] " Bruce Richardson
2022-07-15 16:30   ` 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=5738301.MhkbZ0Pkbq@thomas \
    --to=thomas@monjalon.net \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.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 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.