Re: [PATCH v3 10/17] rv: Fix generated files going over 100 column limit
From: Gabriele Monaco <gmonaco@redhat.com>
Date: 2025-07-15 15:24:18
Also in:
lkml
On Tue, 2025-07-15 at 17:08 +0200, Nam Cao wrote:
On Tue, Jul 15, 2025 at 09:14:27AM +0200, Gabriele Monaco wrote:quoted
The dot2c.py script generates all states in a single line. This breaks the 100 column limit when the state machines are non-trivial. Recent changes allow it to print states over multiple lines if the resulting line would have been too long. Adapt existing monitors with line length over the limit. Signed-off-by: Gabriele Monaco <gmonaco@redhat.com> --- kernel/trace/rv/monitors/sco/sco.h | 12 ++++++++++-- kernel/trace/rv/monitors/snep/snep.h | 14 ++++++++++++-- kernel/trace/rv/monitors/snroc/snroc.h | 12 ++++++++++-- 3 files changed, 32 insertions(+), 6 deletions(-)diff --git a/kernel/trace/rv/monitors/sco/sco.hb/kernel/trace/rv/monitors/sco/sco.h index 7a4c1f2d5ca1c..83ca9a03331af 100644--- a/kernel/trace/rv/monitors/sco/sco.h +++ b/kernel/trace/rv/monitors/sco/sco.h@@ -39,8 +39,16 @@ static const struct automaton_sco automaton_sco= { "schedule_exit" }, .function = { - { thread_context_sco, scheduling_context_sco, INVALID_STATE }, - { INVALID_STATE, INVALID_STATE, thread_context_sco }, + { + thread_context_sco, + scheduling_context_sco, + INVALID_STATE + }, + { + INVALID_STATE, + INVALID_STATE, + thread_context_sco + },I'm confused, these lines were not over 100 columns. Same for snroc. From my understanding of the previous patch, the script does not break lines which are not over the limit. Did I miss something?
Right, I didn't make it obvious in the commit description since I thought it wasn't too important. Those are the monitors whose lines are going to be longer than 100 columns later in the series. Changing it there saves a bit of complication in the next patches, where I only add lines for new events instead of splitting the line /and/ adding the events. Do you think I should mention this in the commit description? Thanks, Gabriele