Remove unnecessary semicolons from Python code in the rvgen tool. Python does not require semicolons to terminate statements, and their presence goes against PEP 8 style guidelines. These semicolons were likely added out of habit from C-style languages.
This cleanup improves consistency with Python coding standards and aligns with the recent improvements to remove other Python anti-patterns from the codebase. Signed-off-by: Wander Lairson Costa <[email protected]> Reviewed-by: Nam Cao <[email protected]> Reviewed-by: Gabriele Monaco <[email protected]> --- tools/verification/rvgen/rvgen/dot2k.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tools/verification/rvgen/rvgen/dot2k.py b/tools/verification/rvgen/rvgen/dot2k.py index e26f2b47390ab..47af9f104a829 100644 --- a/tools/verification/rvgen/rvgen/dot2k.py +++ b/tools/verification/rvgen/rvgen/dot2k.py @@ -46,14 +46,14 @@ class dot2k(Monitor, Dot2c): buff.append("\t/* XXX: validate that this event is only valid in the initial state */") handle = "handle_start_run_event" if self.monitor_type == "per_task": - buff.append("\tstruct task_struct *p = /* XXX: how do I get p? */;"); - buff.append(f"\tda_{handle}(p, {event}{self.enum_suffix});"); + buff.append("\tstruct task_struct *p = /* XXX: how do I get p? */;") + buff.append(f"\tda_{handle}(p, {event}{self.enum_suffix});") elif self.monitor_type == "per_obj": buff.append("\tint id = /* XXX: how do I get the id? */;") buff.append("\tmonitor_target t = /* XXX: how do I get t? */;") buff.append(f"\tda_{handle}(id, t, {event}{self.enum_suffix});") else: - buff.append(f"\tda_{handle}({event}{self.enum_suffix});"); + buff.append(f"\tda_{handle}({event}{self.enum_suffix});") buff.append("}") buff.append("") return '\n'.join(buff) -- 2.53.0
