From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH] devtools: list symbols by version
Date: Tue, 15 Aug 2023 12:01:50 +0200 [thread overview]
Message-ID: <CAJFAV8y1dDu02h__SuvNhjnmtjQjJggCLhr7bxHaSiWQ-W0qcw@mail.gmail.com> (raw)
In-Reply-To: <10436637.nUPlyArG6x@thomas>
On Mon, Aug 14, 2023 at 11:49 AM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> vendredi 11 août 2023, David Marchand:
> > Make it easier to list experimental symbols added in a certain version.
> > While at it, add a check on map symbol files content to avoid breaking
> > this listing tool.
>
> Is there a relation between the new check and the new -V option?
> I feel it would be clearer in 2 separate patches.
The new option relies on a strict format in the .map files.
I could add the check first in a separate patch if you prefer.
--
David Marchand
next prev parent reply other threads:[~2023-08-15 10:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 15:49 David Marchand
2023-08-11 17:13 ` Stephen Hemminger
2023-08-14 9:48 ` Thomas Monjalon
2023-08-15 10:01 ` David Marchand [this message]
2023-08-15 10:36 ` [PATCH v2 1/2] devtools: add check on symbol maps format David Marchand
2023-08-15 10:36 ` [PATCH v2 2/2] devtools: list symbols by version David Marchand
2023-08-15 17:42 ` [PATCH v3 1/2] devtools: add check on symbol maps format David Marchand
2023-08-15 17:42 ` [PATCH v3 2/2] devtools: list symbols by version David Marchand
2023-08-16 7:16 ` [PATCH v4 1/2] devtools: add check on symbol maps format David Marchand
2023-08-16 7:16 ` [PATCH v4 2/2] devtools: list symbols by version David Marchand
2023-11-15 10:42 ` [PATCH v5 1/2] devtools: add check on symbol maps format David Marchand
2023-11-15 10:42 ` [PATCH v5 2/2] devtools: list symbols by version David Marchand
2023-11-27 7:37 ` 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=CAJFAV8y1dDu02h__SuvNhjnmtjQjJggCLhr7bxHaSiWQ-W0qcw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--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).