From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Christoph Hellwig <hch@infradead.org>,
Paul Mundt <lethal@linux-sh.org>,
Andrew Morton <akpm@linux-foundation.org>,
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 08:47:06 +0100 [thread overview]
Message-ID: <20071019074706.GA10446@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20071018160050.GA18508@infradead.org>
On Thu, Oct 18, 2007 at 05:00:50PM +0100, Christoph Hellwig wrote:
> On Thu, Oct 18, 2007 at 04:54:29PM +0100, Russell King wrote:
> > What would be good is if some effort could be made by the utrace-
> > interested parties to make the transition to utrace much less painful.
> > For instance, I quite like the getregs/setregs abstractions, and it
> > looks like these *could* be self-contained in a single patch. It
> > would be nice if we could move architectures over to this one a time.
> > Once that's in, that's one chunk of utrace merged.
>
> Alexey Dobriyan had some patches to implement regsets, and these were
> posted here on lkml.
Given that not all architecture maintainers read lkml, and they are
patches affecting all *architectures*, wouldn't it have been a good
idea if they'd copied linux-arch?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2007-10-19 7:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4713B238.4030409@windriver.com>
2007-10-18 4:20 ` [PATCH 0/21] KGDB: Request to merge KGDB Andrew Morton
2007-10-18 15:23 ` Paul Mundt
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 [this message]
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=20071019074706.GA10446@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=jason.wessel@windriver.com \
--cc=lethal@linux-sh.org \
--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 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).