Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Helge Deller <deller@gmx.de>,
	linux-parisc@vger.kernel.org, kyle@hera.kernel.org,
	randolph@tausq.org, stable@kernel.org
Subject: Re: [PATCH] parisc: fix kernel crash when unwinding a userspace process (v2)
Date: Fri, 21 Nov 2008 22:53:01 -0700	[thread overview]
Message-ID: <20081122055301.GA12724@colo.lackof.org> (raw)
In-Reply-To: <20081121142013.f8d59b3f.akpm@linux-foundation.org>

On Fri, Nov 21, 2008 at 02:20:13PM -0800, Andrew Morton wrote:
...
> > > Why has a fix for such a severe bug been floating around unmerged for
> > > such a long time?

Three people are listed for parisc-linux in MAINTAINERS.
My understanding was Kyle would integrate and push patches.
Willy and I would help by reviewing code, testing and misc crap.

I asked if I should ACK parisc specific patches and was told in general
I didn't need to. I will start sending "Reviewed By:" when I feel
I understand what a patch fixes and that it's correct (even if not perfect).

> > I've tried to push it upstream a few times...
> 
> OK, well I'll merge it next week unless someone stops me.

I won't stop you. :)
Based on this posting:
    http://marc.info/?l=linux-parisc&m=122726233324164&w=2

you can add:
   Review-by: Randolph Chung <randolph@tausq.org>

I trust Randolph - he used to have commit access to the parisc-linux.org
CVS tree when we still used one.

And Helge has been great about fixing stuff - much better than the three
listed maintainers lately.
Kyle, willy, any objection to adding Helge to the MAINTAINERS list
for PARISC port?
I'd rather allow Helge to make a few small mistakes occasionally rather
than watch his parisc specific patches fall on the floor.

thanks,
grant

  reply	other threads:[~2008-11-22  5:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-20 21:58 [PATCH] parisc: fix kernel crash when unwinding a userspace process Helge Deller
2008-11-21 10:11 ` Randolph Chung
2008-11-21 14:02   ` Helge Deller
2008-11-21 14:16 ` [PATCH] parisc: fix kernel crash when unwinding a userspace process (v2) Helge Deller
2008-11-21 19:17   ` Andrew Morton
2008-11-21 22:00     ` Helge Deller
2008-11-21 22:20       ` Andrew Morton
2008-11-22  5:53         ` Grant Grundler [this message]
2008-11-22 12:22           ` Matthew Wilcox
2008-11-22 18:01             ` Grant Grundler
2008-11-22 20:09               ` Helge Deller
2008-12-01  7:21               ` [PATCH] 2.6.28-rc6 update parisc MAINTAINERS Grant Grundler
2008-12-01 15:59                 ` Helge Deller
2008-12-03  8:22                   ` Grant Grundler
2008-11-25 17:20           ` [PATCH] parisc: fix kernel crash when unwinding a userspace process (v2) Kyle McMartin
2008-11-26  2:47             ` Grant Grundler
2008-11-26  2:59               ` Kyle McMartin
2008-11-25 17:03 ` [PATCH] parisc: fix kernel crash when unwinding a userspace process Kyle McMartin

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=20081122055301.GA12724@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=akpm@linux-foundation.org \
    --cc=deller@gmx.de \
    --cc=kyle@hera.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=randolph@tausq.org \
    --cc=stable@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