The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: PATCH: Minimal fix for sysrq on serial console hang
Date: Wed, 12 Jul 2006 15:01:32 +0100	[thread overview]
Message-ID: <20060712140132.GB11047@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1152713491.22943.72.camel@localhost.localdomain>

On Wed, Jul 12, 2006 at 03:11:31PM +0100, Alan Cox wrote:
> Ar Mer, 2006-07-12 am 14:47 +0100, ysgrifennodd Russell King:
> > On Wed, Jul 12, 2006 at 02:54:21PM +0100, Alan Cox wrote:
> > > When I originally did this change I used oops_in_progress as a locking
> > > guide. However it turns out there is one other place that turns all the
> > > locking on its head and that is sysrq.
> > 
> > Well, akpm's had a fix in his tree for some time, which he's been
> > pestering me with, so I committed that a few days ago:
> 
> 
> Even better, thanks hadn't seen that go in.

It's not in Linus' tree just yet - I asked Linus to pull stuff last night.
However, since upgrading FC2 to FC5 (which took anaconda some 4 hours
on a 2.6GHz P4) and thereby moving off my ancient git/cogito version,
various scripts broke and didn't produce the nice requests for Linus.
I guess Linus wasn't too happy about pulling my git trees with only
having a diffstat of what was there...

Maybe something will happen tonight though.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

      reply	other threads:[~2006-07-12 14:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-12 13:54 PATCH: Minimal fix for sysrq on serial console hang Alan Cox
2006-07-12 13:47 ` Russell King
2006-07-12 14:11   ` Alan Cox
2006-07-12 14:01     ` Russell King [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=20060712140132.GB11047@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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