From: Jason Wessel <jason.wessel@windriver.com>
To: Tim Bird <tim.bird@am.sony.com>
Cc: "kgdb-bugreport@lists.sourceforge.net"
<kgdb-bugreport@lists.sourceforge.net>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Fwd: [PATCH] kdb: Avoid using dbg_io_ops until it is initialized
Date: Tue, 20 Mar 2012 12:14:35 -0500 [thread overview]
Message-ID: <4F68BAFB.7070301@windriver.com> (raw)
In-Reply-To: <4F68B180.8030709@am.sony.com>
On 03/20/2012 11:34 AM, Tim Bird wrote:
> Jason,
>
> This patch has apparently fallen through the cracks. Can you please apply?
> This fixes a kernel panic for a use case where I'm setting a breakpoint
> from kdb_cmds on kernel startup. In this case, without this patch
> dbg_io_ops is used before it is initialized.
Many thanks Tim.
I'll review/regression test this and add it to the merge queue. I found another patch from you in the same week from last year that I will also review. I am not exactly sure why these never made it to my review list, but what once was lost is now found.
Cheers,
Jason.
prev parent reply other threads:[~2012-03-20 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 16:34 Fwd: [PATCH] kdb: Avoid using dbg_io_ops until it is initialized Tim Bird
2012-03-20 17:14 ` Jason Wessel [this message]
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=4F68BAFB.7070301@windriver.com \
--to=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.bird@am.sony.com \
/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;
as well as URLs for NNTP newsgroup(s).