On Fri, 14 Nov 2014 07:31:46 -0500
Steven Rostedt wrote:
> On Fri, 14 Nov 2014 12:13:51 +
> Daniel Thompson wrote:
>
> > BTW I did check on kernel.org before punting them back on the list:
> > https://git.kernel.org/cgit/linux/kernel/git/rostedt/linux-trace.git/log/?h=for-next
> >
> > Am
On Fri, 14 Nov 2014 12:13:51 +
Daniel Thompson wrote:
> BTW I did check on kernel.org before punting them back on the list:
> https://git.kernel.org/cgit/linux/kernel/git/rostedt/linux-trace.git/log/?h=for-next
>
> Am I looking in the wrong place or are they not aimed at linux-next just
>
On 14/11/14 11:59, Steven Rostedt wrote:
> On Fri, 14 Nov 2014 09:08:21 +
> Daniel Thompson wrote:
>
>> On 14/11/14 02:26, Steven Rostedt wrote:
>>> On Thu, 6 Nov 2014 12:41:55 +
>>> Daniel Thompson wrote:
>>>
Currently kdb's ftdump command unconditionally crashes due to a null
On Fri, 14 Nov 2014 09:08:21 +
Daniel Thompson wrote:
> On 14/11/14 02:26, Steven Rostedt wrote:
> > On Thu, 6 Nov 2014 12:41:55 +
> > Daniel Thompson wrote:
> >
> >> Currently kdb's ftdump command unconditionally crashes due to a null
> >> pointer de-reference whenever the command is
On 14/11/14 02:26, Steven Rostedt wrote:
> On Thu, 6 Nov 2014 12:41:55 +
> Daniel Thompson wrote:
>
>> Currently kdb's ftdump command unconditionally crashes due to a null
>> pointer de-reference whenever the command is run. This in turn causes
>> the kernel to panic.
>>
>> The abridged
On 14/11/14 02:26, Steven Rostedt wrote:
On Thu, 6 Nov 2014 12:41:55 +
Daniel Thompson daniel.thomp...@linaro.org wrote:
Currently kdb's ftdump command unconditionally crashes due to a null
pointer de-reference whenever the command is run. This in turn causes
the kernel to panic.
The
On Fri, 14 Nov 2014 09:08:21 +
Daniel Thompson daniel.thomp...@linaro.org wrote:
On 14/11/14 02:26, Steven Rostedt wrote:
On Thu, 6 Nov 2014 12:41:55 +
Daniel Thompson daniel.thomp...@linaro.org wrote:
Currently kdb's ftdump command unconditionally crashes due to a null
On 14/11/14 11:59, Steven Rostedt wrote:
On Fri, 14 Nov 2014 09:08:21 +
Daniel Thompson daniel.thomp...@linaro.org wrote:
On 14/11/14 02:26, Steven Rostedt wrote:
On Thu, 6 Nov 2014 12:41:55 +
Daniel Thompson daniel.thomp...@linaro.org wrote:
Currently kdb's ftdump command
On Fri, 14 Nov 2014 12:13:51 +
Daniel Thompson daniel.thomp...@linaro.org wrote:
BTW I did check on kernel.org before punting them back on the list:
https://git.kernel.org/cgit/linux/kernel/git/rostedt/linux-trace.git/log/?h=for-next
Am I looking in the wrong place or are they not aimed
On Fri, 14 Nov 2014 07:31:46 -0500
Steven Rostedt rost...@goodmis.org wrote:
On Fri, 14 Nov 2014 12:13:51 +
Daniel Thompson daniel.thomp...@linaro.org wrote:
BTW I did check on kernel.org before punting them back on the list:
On Thu, 6 Nov 2014 12:41:55 +
Daniel Thompson wrote:
> Currently kdb's ftdump command unconditionally crashes due to a null
> pointer de-reference whenever the command is run. This in turn causes
> the kernel to panic.
>
> The abridged stacktrace (gathered with ARCH=arm) is:
> --- cut here
On Thu, 6 Nov 2014 12:41:55 +
Daniel Thompson daniel.thomp...@linaro.org wrote:
Currently kdb's ftdump command unconditionally crashes due to a null
pointer de-reference whenever the command is run. This in turn causes
the kernel to panic.
The abridged stacktrace (gathered with
12 matches
Mail list logo