>-----Original Message-----
>From: Ankur Dwivedi <adwiv...@marvell.com>
>Sent: Friday, December 15, 2023 12:14 PM
>To: dev@dpdk.org
>Cc: tho...@monjalon.net; Jerin Jacob Kollanukkaran <jer...@marvell.com>;
>Ankur Dwivedi <adwiv...@marvell.com>
>Subject: [PATCH v6 0/2] devtools: add tracepoint check in checkpatch
>
>This patch series adds a validation in checkpatch tool to check if tracepoint 
>is
>present in any new function added in ethdev, eventdev cryptodev and
>mempool library.

Please let me know if this patch series can be merged in DPDK or if there are 
any comments.
>
>v6:
> - The build_map_changes function is moved from check-symbol-change.sh to
>   a new symbol-map-util.sh file. This function can be used in other
>   scripts by including symbol-map-util.sh file.
>
>v5:
> - Copied the build_map_changes function from check-symbol-change.sh to
>   check-tracepoint.sh.
> - Added eventdev, cryptodev and mempool in libdir in check-tracepoint.sh.
>
>v4:
> - Rebased on the recent next-net branch.
> - Refined logic to find function definition.
> - Updated year in the license in devtools/check-tracepoint.sh.
> - Removed cryptodev, added ethdev in libdir in
>   devtools/check-tracepoint.sh.
>
>v3:
> - Split the v2 patch into 2 patches.
> - The file common-func.sh is renamed to build-symbol-map.sh.
> - Removed check-tracepoint.py file.
> - Code improvements in check-tracepoint.sh.
>
>v2:
> - Add check for parent directory.
>
>Ankur Dwivedi (2):
>  devtools: move build map changes function
>  devtools: add tracepoint check in checkpatch
>
> devtools/check-symbol-change.sh |  76 +---------------
> devtools/check-tracepoint.sh    | 148 ++++++++++++++++++++++++++++++++
> devtools/checkpatches.sh        |   9 ++
> devtools/symbol-map-util.sh     |  78 +++++++++++++++++
> devtools/trace-skiplist.txt     |   0
> 5 files changed, 237 insertions(+), 74 deletions(-)  create mode 100755
>devtools/check-tracepoint.sh  create mode 100644 devtools/symbol-map-
>util.sh  create mode 100644 devtools/trace-skiplist.txt
>
>--
>2.25.1

Reply via email to