On Wed, Mar 12, 2014 at 5:53 PM, Steven Rostedt wrote:
> Your timing here isn't that great either, because I leave tomorrow for
> another conference, and I'm currently trying to get everything ready
> for that trip. Could you ping me again on Tuesday?
Hey Steven
It's your friendly reminder to lo
On Wed, Mar 12, 2014 at 5:53 PM, Steven Rostedt wrote:
> Your timing here isn't that great either, because I leave tomorrow for
> another conference, and I'm currently trying to get everything ready
> for that trip. Could you ping me again on Tuesday?
Will do.
Vaibhav
--
To unsubscribe from this
On Wed, 12 Mar 2014 17:16:20 -0700
Vaibhav Nagarnaik wrote:
> Hi Steven,
>
> Any chance you can take a look at this patch?
>
Grumble, I thought I pulled this in already. I may have been working on
it and then got distracted by my day job, and it got lost in the
shuffle.
Your timing here isn't
Hi Steven,
Any chance you can take a look at this patch?
Thanks
Vaibhav
On Thu, Feb 13, 2014 at 7:51 PM, Vaibhav Nagarnaik
wrote:
> In event format strings, the array size is reported in two locations.
> One in array subscript and then via the "size:" attribute. The values
> reported there h
In event format strings, the array size is reported in two locations.
One in array subscript and then via the "size:" attribute. The values
reported there have a mismatch.
For e.g., in sched:sched_switch the prev_comm and next_comm character
arrays have subscript values as [32] where as the actual
In event format strings, the array size is reported in two locations.
One in array subscript and then via the "size:" attribute. The values
reported there have a mismatch.
For e.g., in sched:sched_switch the prev_comm and next_comm character
arrays have subscript values as [32] where as the actual
6 matches
Mail list logo