[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220318095817.4ad3a65a@gandalf.local.home>
Date: Fri, 18 Mar 2022 09:58:17 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Wolfram Sang <wsa@...nel.org>
Cc: Jae Hyun Yoo <quic_jaehyoo@...cinc.com>,
Ingo Molnar <mingo@...hat.com>,
Jamie Iles <quic_jiles@...cinc.com>,
Graeme Gregory <quic_ggregory@...cinc.com>,
linux-kernel@...r.kernel.org, linux-i2c@...r.kernel.org
Subject: Re: [PATCH v2] i2c: add tracepoints for I2C slave events
On Fri, 18 Mar 2022 11:53:48 +0100
Wolfram Sang <wsa@...nel.org> wrote:
> > trace printings can be selected by adding a filter like:
> >
> > echo adapter_nr==1 >/sys/kernel/tracing/events/i2c_slave/filter
> >
> > Signed-off-by: Jae Hyun Yoo <quic_jaehyoo@...cinc.com>
>
> Steven, are you happy with the tracepoint parts of this patch?
Strange. I do not have v2 in my inbox anywhere. I checked the spam folders
and found nothing. I had a glitch in my mail server around this time and
maybe it was dropped then.
Let me take a look at it in my LMKL folder, which it appears to be there :-/
-- Steve
>
>
> > + if (trace_i2c_slave_enabled() && !ret)
> > + trace_i2c_slave(client, event, val);
>
> Why '!ret'? I think we should always print 'ret' in the trace as well.
> Backends are allowed to send errnos on WRITE_RECEIVED to NACK the
> reception of a byte. This is useful information, too, or?
>
> Rest looks good to me.
>
> Thanks,
>
> Wolfram
>
Powered by blists - more mailing lists