From: Piet Delaney <piet@bluelane.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Piet Delaney <piet@bluelane.com>,
vgoyal@in.ibm.com, George Anzinger <george@wildturkeyranch.net>,
Discussion "list for crash utility usage,
maintenance and development" <crash-utility@redhat.com>,
kgdb-bugreport@lists.sourceforge.net,
Subhachandra Chandra <schandra@bluelane.com>,
linux-kernel@vger.kernel.org
Subject: Re: How about an enumerated list of issues with the existing kgdb patches?
Date: Wed, 13 Dec 2006 00:32:58 -0800 [thread overview]
Message-ID: <1165998778.25954.12.camel@piet2.bluelane.com> (raw)
In-Reply-To: <20060830200020.cd5bb3d7.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 2197 bytes --]
On Wed, 2006-08-30 at 20:00 -0700, Andrew Morton wrote:
> On Wed, 30 Aug 2006 19:42:32 -0700
> Piet Delaney <piet@bluelane.com> wrote:
>
> > On Wed, 2006-08-30 at 15:57 -0700, Andrew Morton wrote:
> > > On Wed, 30 Aug 2006 14:48:22 -0700
> > > Andrew Morton <akpm@osdl.org> wrote:
> > >
> > > > Plus: I'd want to see a maintainance person or team who
> > > > respond promptly to email and who remain reasonably engaged with what's
> > > > going on in the mainline kernel. Because if problems crop up (and they
> > > > will), I don't want to have to be the bunny who has to worry about them...
> > >
> > > umm, clarification needed here.
> > >
> > > No criticism of the present maintainers intended! Last time I grabbed the
> > > kgdb patches from sf.net they applied nicely, worked quite reliably (much
> > > better than the old ones I'd been trying to sustain) and had been
> > > tremendously cleaned up.
> >
> > So why did you stop including them in the mm patch?
>
> Some change in 2.6.17-pre caused it to all stop working.
>
> > I recall your quality issue and Tom was all in favor
> > of resolving them. Was it too much work cleaning up the
> > patches to meet your needs that lead to the patch being
> > dropped from the mm series?
>
> It all seems reasonably clean now, but I haven't looked closely (nor have I
> had to)
Any suggestions on how to progress?
>
> > kgdb over ethernet is working great, and it looks like there
> > is plenty of support on the SF mailing list.
>
> good.
>
> > >
> > > It's a big step.
> >
> > How about a concrete list of patch quality issues that the group
> > can address to allow your weekly addition to the mm patch as a
> > set toward eventually integration.
>
> >From whom? me?
>
> > Wouldn't getting kgdb back into the mm patch series be a reasonable
> > first step eventual maintenance in kernel.org?
>
> Is on my todo list somewhere.
--
Piet Delaney Phone: (408) 200-5256
Blue Lane Technologies Fax: (408) 200-5299
10450 Bubb Rd.
Cupertino, Ca. 95014 Email: piet@bluelane.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-12-13 8:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44EC8CA5.789286A@redhat.com>
[not found] ` <20060824111259.GB22145@in.ibm.com>
[not found] ` <44EDA676.37F12263@redhat.com>
[not found] ` <1156966522.29300.67.camel@piet2.bluelane.com>
[not found] ` <20060830204032.GD30392@in.ibm.com>
2006-08-30 21:41 ` [RFC] [Crash-utility] Patch to use gdb's bt in crash - works great with kgdb! - KGDB in Linus Kernel Piet Delaney
2006-08-30 21:48 ` Andrew Morton
2006-08-30 22:57 ` Andrew Morton
2006-08-31 2:42 ` How about an enumerated list of issues with the existing kgdb patches? Piet Delaney
2006-08-31 3:00 ` Andrew Morton
2006-12-13 8:32 ` Piet Delaney [this message]
2006-08-30 21:53 ` [RFC] [Crash-utility] Patch to use gdb's bt in crash - works great with kgdb! - KGDB in Linus Kernel Randy.Dunlap
2006-08-30 22:22 ` Piet Delaney
2006-08-31 14:07 ` Andi Kleen
2006-08-31 14:20 ` [Kgdb-bugreport] " Tom Rini
2006-08-31 14:43 ` Andi Kleen
2006-08-31 20:41 ` Piet Delaney
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=1165998778.25954.12.camel@piet2.bluelane.com \
--to=piet@bluelane.com \
--cc=akpm@osdl.org \
--cc=crash-utility@redhat.com \
--cc=george@wildturkeyranch.net \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=schandra@bluelane.com \
--cc=vgoyal@in.ibm.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
all inboxes | Powered by JetHome®