On Wed, 21 May 2014 09:26:41 +0100
Javi Merino wrote:
> Hi Steve,
>
> On Wed, May 21, 2014 at 03:07:23AM +0100, Steven Rostedt wrote:
> > Hmm, I didn't think about cross tree dependencies. I already pushed this
> > patch to my for-next branch which is already in linux-next, and I do not
> >
On Wed, 21 May 2014 09:26:41 +0100
Javi Merino javi.mer...@arm.com wrote:
Hi Steve,
On Wed, May 21, 2014 at 03:07:23AM +0100, Steven Rostedt wrote:
Hmm, I didn't think about cross tree dependencies. I already pushed this
patch to my for-next branch which is already in linux-next, and I do
Hi Steve,
On Wed, May 21, 2014 at 03:07:23AM +0100, Steven Rostedt wrote:
> Hmm, I didn't think about cross tree dependencies. I already pushed this
> patch to my for-next branch which is already in linux-next, and I do not
> rebase this branch unless there's a really good need to.
>
> I guess I
Hi Steve,
On Wed, May 21, 2014 at 03:07:23AM +0100, Steven Rostedt wrote:
Hmm, I didn't think about cross tree dependencies. I already pushed this
patch to my for-next branch which is already in linux-next, and I do not
rebase this branch unless there's a really good need to.
I guess I
Hmm, I didn't think about cross tree dependencies. I already pushed this
patch to my for-next branch which is already in linux-next, and I do not
rebase this branch unless there's a really good need to.
I guess I needed to make a separate branch that you could have pulled
separately. I'm not sure
From: "Steven Rostedt (Red Hat)"
Being able to show a cpumask of events can be useful as some events
may affect only some CPUs. There is no standard way to record the
cpumask and converting it to a string is rather expensive during
the trace as traces happen in hotpaths. It would be better to
From: Steven Rostedt (Red Hat) rost...@goodmis.org
Being able to show a cpumask of events can be useful as some events
may affect only some CPUs. There is no standard way to record the
cpumask and converting it to a string is rather expensive during
the trace as traces happen in hotpaths. It
Hmm, I didn't think about cross tree dependencies. I already pushed this
patch to my for-next branch which is already in linux-next, and I do not
rebase this branch unless there's a really good need to.
I guess I needed to make a separate branch that you could have pulled
separately. I'm not sure
8 matches
Mail list logo