On 14/11/14 11:59, Steven Rostedt wrote: > On Fri, 14 Nov 2014 09:08:21 +0000 > Daniel Thompson <[email protected]> wrote: > >> On 14/11/14 02:26, Steven Rostedt wrote: >>> On Thu, 6 Nov 2014 12:41:55 +0000 >>> Daniel Thompson <[email protected]> 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 --- >>> >>> This is a nasty line. "git am " truncated the change log there thinking >>> it was the end of the change log (that '---' did it). >> >> Oops. Looks like I shall have to train myself out of that particular >> habit (which will be tough, since I've used it long enough to be ingrained). >> >> Will repost as soon as I've thought about your other comments. > > I was just telling you so that you wouldn't do it again. I already > pulled in your patches. You didn't need to resend. But at least it > would help you get out of that habit! J
Thanks. 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 yet? Daniel. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
