From: Paul Mundt <lethal@linux-sh.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jason Wessel <jason.wessel@windriver.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-arch@vger.kernel.org
Subject: Re: [PATCH 0/21] KGDB: Request to merge KGDB
Date: Fri, 19 Oct 2007 00:23:10 +0900 [thread overview]
Message-ID: <20071018152310.GA7299@linux-sh.org> (raw)
In-Reply-To: <20071017212025.d8a52694.akpm@linux-foundation.org>
On Wed, Oct 17, 2007 at 09:20:25PM -0700, Andrew Morton wrote:
> On Mon, 15 Oct 2007 13:32:24 -0500 Jason Wessel <jason.wessel@windriver.com> wrote:
> > This is a request to merge KGDB into the mainline kernel.
>
> This won't work very well. There's a lot of review work to be done here,
> and a lot of it by busy architecture maintainers. Expecting people to do
> all this review and test work late in the merge window when they're all
> madly scrambling to get their bugs^Wpatches into mainline is not reasonable.
> This should all have started a month ago.
>
> So we're looking at a 2.6.25 merge for this work. After this round of
> review has settled, please upissue the patches and keep linux-arch (cc'ed
> here) copied on everything, thanks.
>
It would also be nice to balance this out with the utrace merge, as both
are going to cause quite a lot of pain on the architecture side.
next prev parent reply other threads:[~2007-10-18 15:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 18:32 [PATCH 0/21] KGDB: Request to merge KGDB Jason Wessel
2007-10-18 4:20 ` Andrew Morton
2007-10-18 15:23 ` Paul Mundt [this message]
2007-10-18 15:25 ` Christoph Hellwig
2007-10-18 15:54 ` Russell King
2007-10-18 16:00 ` Christoph Hellwig
2007-10-19 7:47 ` Russell King
2007-10-23 18:31 ` Pavel Machek
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=20071018152310.GA7299@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=akpm@linux-foundation.org \
--cc=jason.wessel@windriver.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.