From: Daniel Thompson <daniel.thompson@linaro.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>,
kgdb-bugreport@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
patches@linaro.org, linaro-kernel@lists.linaro.org,
John Stultz <john.stultz@linaro.org>,
Sumit Semwal <sumit.semwal@linaro.org>,
Jason Wessel <jason.wessel@windriver.com>
Subject: Re: [PATCH RESEND 3.18-rc3 v2 0/2] trace: kdb: Bug fixes for ftdump
Date: Mon, 10 Nov 2014 09:41:32 +0000 [thread overview]
Message-ID: <5460884C.1050401@linaro.org> (raw)
In-Reply-To: <20141106082728.5d4b7161@gandalf.local.home>
On 06/11/14 13:27, Steven Rostedt wrote:
> On Thu, 6 Nov 2014 12:41:54 +0000
> Daniel Thompson <daniel.thompson@linaro.org> wrote:
>
>> This patchset makes it possible to use kdb's ftdump command without
>> panicing, crashing or livelocking. The ftdump command cannot be used
>> at all without these changes.
>>
>> IIRC this patches are still pending Jason's ack.
>
> I haven't heard from Jason in a long time. Is he still active?
[sorry for the delay, I wanted to give Jason a chance to answer this]
Very occasionally.
I can't find anything on lkml in the last three months, and I have
unreviewed kdb patches that stretch back well beyond that.
That said he still helps people on kgdb-bugreport@ from time-to-time
(and as recently as last week). I've also had a little bit of private
contact although nothing very recent.
On that basis I'd say you shouldn't feel guilty if you have to accept a
change here without an ack.
Daniel.
next prev parent reply other threads:[~2014-11-10 9:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 14:44 [PATCH 3.17-rc4] trace: kdb: Fix kernel panic during ftdump Daniel Thompson
2014-09-24 10:32 ` [PATCH 3.17-rc4 v2 0/2] trace: kdb: Bug fixes for ftdump Daniel Thompson
2014-09-24 10:33 ` [PATCH 3.17-rc4 v2 1/2] trace: kdb: Fix kernel panic during ftdump Daniel Thompson
2014-09-24 10:33 ` [PATCH 3.17-rc4 v2 2/2] trace: kdb: Fix kernel livelock with empty buffers Daniel Thompson
2014-09-24 15:07 ` [PATCH 3.17-rc4 v2 0/2] trace: kdb: Bug fixes for ftdump Steven Rostedt
2014-09-24 15:09 ` Daniel Thompson
2014-11-06 12:41 ` [PATCH RESEND 3.18-rc3 " Daniel Thompson
2014-11-06 12:41 ` [PATCH RESEND 3.18-rc3 v2 1/2] trace: kdb: Fix kernel panic during ftdump Daniel Thompson
2014-11-14 2:26 ` Steven Rostedt
2014-11-14 9:08 ` Daniel Thompson
2014-11-14 11:59 ` Steven Rostedt
2014-11-14 12:13 ` Daniel Thompson
2014-11-14 12:31 ` Steven Rostedt
2014-11-14 12:35 ` Steven Rostedt
2014-11-06 12:41 ` [PATCH RESEND 3.18-rc3 v2 2/2] trace: kdb: Fix kernel livelock with empty buffers Daniel Thompson
2014-11-06 13:27 ` [PATCH RESEND 3.18-rc3 v2 0/2] trace: kdb: Bug fixes for ftdump Steven Rostedt
2014-11-10 9:41 ` Daniel Thompson [this message]
2014-11-14 2:16 ` Steven Rostedt
2014-11-14 11:03 ` Daniel Thompson
2014-11-14 11:21 ` [PATCH 3.18-rc3 v3 " Daniel Thompson
2014-11-14 11:21 ` [PATCH 3.18-rc3 v3 1/2] trace: kdb: Fix kernel panic during ftdump Daniel Thompson
2014-11-14 11:21 ` [PATCH 3.18-rc3 v3 2/2] trace: kdb: Fix kernel livelock with empty buffers Daniel Thompson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5460884C.1050401@linaro.org \
--to=daniel.thompson@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=jason.wessel@windriver.com \
--cc=john.stultz@linaro.org \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=patches@linaro.org \
--cc=rostedt@goodmis.org \
--cc=sumit.semwal@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox