> fix some memleaks in parse_events_term__sym_hw and parse_events_term__clone.

Can it be more appropriate to refer to the term “memory leak” in consistent 
ways?


> v1 ==> v2
> 1. split into two patches

Corresponding development consequences can become more interesting.


> v2 ==> v3
> add more commit log.
>
> Chen Wandun (1):
>   perf tools: fix potential memleak in perf events parser
>
> Cheng Jian (1):
>   perf tools: fix potential memleak in perf events parser
>
>  tools/perf/util/parse-events.c | 51 ++++++++++++++++++++++++++++------

Are there any chances to make the change distinction a bit easier
by adjusting such commit subjects?

Regards,
Markus

Reply via email to