Re: [PATCH 08/26 v5] tracing: Do not check return values of trace_seq_p*() for mmio tracer

2014-11-18 Thread Petr Mladek
On Fri 2014-11-14 23:58:55, Steven Rostedt wrote: > From: "Steven Rostedt (Red Hat)" > > The return values for trace_seq_printf() and friends are going to be > removed and they will become void functions. The mmio tracer checked > their return and even did so incorrectly. > > Some of the

Re: [PATCH 08/26 v5] tracing: Do not check return values of trace_seq_p*() for mmio tracer

2014-11-18 Thread Petr Mladek
On Fri 2014-11-14 23:58:55, Steven Rostedt wrote: From: Steven Rostedt (Red Hat) rost...@goodmis.org The return values for trace_seq_printf() and friends are going to be removed and they will become void functions. The mmio tracer checked their return and even did so incorrectly. Some of

[PATCH 08/26 v5] tracing: Do not check return values of trace_seq_p*() for mmio tracer

2014-11-14 Thread Steven Rostedt
From: "Steven Rostedt (Red Hat)" The return values for trace_seq_printf() and friends are going to be removed and they will become void functions. The mmio tracer checked their return and even did so incorrectly. Some of the funtions which returned the values were never checked themselves.

[PATCH 08/26 v5] tracing: Do not check return values of trace_seq_p*() for mmio tracer

2014-11-14 Thread Steven Rostedt
From: Steven Rostedt (Red Hat) rost...@goodmis.org The return values for trace_seq_printf() and friends are going to be removed and they will become void functions. The mmio tracer checked their return and even did so incorrectly. Some of the funtions which returned the values were never checked