Re: [PATCH 0/7] seq_file .next functions should increase position index

[Vasily Averin <vvs@virtuozzo.com>]

On 1/24/20 6:50 PM, Steven Rostedt wrote:
> On Fri, 24 Jan 2020 10:02:36 +0300
> Vasily Averin <vvs@virtuozzo.com> wrote:
> 
>>
>> I've sent patches into maillists of affected subsystems already,
>> this patch-set fixes the problem in files related to 
>> pstore, tracing, gcov, sysvipc  and other subsystems processed 
>> via linux-kernel@ mailing list directly
> 
> Since you sent the patches out individually, and not as the usually way
> of replying to the 0/7 patch (this email), do you expect the patches to
> just be accepted by the individual maintainers, and not as a series?

Yes, you are right, I've missed it.
Could you please review tracing-related patches of this patch set?

>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=206283
>>
>> Vasily Averin (7):
>>   pstore_ftrace_seq_next should increase position index
>>   gcov_seq_next should increase position index
>>   t_next should increase position index
>>   fpid_next should increase position index
>>   eval_map_next should increase position index
>>   trigger_next should increase position index
>>   sysvipc_find_ipc should increase position index
>>
>>  fs/pstore/inode.c                   | 2 +-
>>  ipc/util.c                          | 2 +-
>>  kernel/gcov/fs.c                    | 2 +-
>>  kernel/trace/ftrace.c               | 9 ++++++---
>>  kernel/trace/trace.c                | 4 +---
>>  kernel/trace/trace_events_trigger.c | 5 +++--
>>  6 files changed, 13 insertions(+), 11 deletions(-)
>>
>