All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <iod00d@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH&RFC 2/2] OS_MCA Recovery from poisoned memory read
Date: Thu, 05 Aug 2004 18:49:33 +0000	[thread overview]
Message-ID: <20040805184933.GG6526@cup.hp.com> (raw)
In-Reply-To: <41121484.40804@jp.fujitsu.com>

On Thu, Aug 05, 2004 at 08:05:40PM +0900, Hidetoshi Seto wrote:
> The MCA offending process will restart from handler_bh, and
> will suicide after isolating the poisoned page.

Hidetoshi,
Wow! I'm impressed - this is amazing functionality.

I only noticed the three new driver files didn't have either
a copyright nor license embedded in it.

I'm told the license is optional because the "linux-2,6/COPYING"
contains a blanket statement for the rest of the kernel.
But many lawyers still like to see it in each file.

grant

> +++ linux-2.6.8-rc3-mcadrv-v2/arch/ia64/kernel/mca_drv.c	2004-08-04 19:17:09.676773696 +0900
> @@ -0,0 +1,647 @@
> +/*
> + * File:	mca_drv.c
> + * Purpose:	Generic MCA handling layer
> + */
...

> --- linux-2.6.8-rc3/arch/ia64/kernel/mca_drv.h	1970-01-01 09:00:00.000000000 +0900
> +++ linux-2.6.8-rc3-mcadrv-v2/arch/ia64/kernel/mca_drv.h	2004-08-04 18:08:39.000000000 +0900
> @@ -0,0 +1,111 @@
...

> +/*
> + * File:	mca_drv.h
> + * Purpose:	Define helpers for Generic MCA handling
> + */
...

> --- linux-2.6.8-rc3/arch/ia64/kernel/mca_drv_asm.S	1970-01-01 09:00:00.000000000 +0900
> +++ linux-2.6.8-rc3-mcadrv-v2/arch/ia64/kernel/mca_drv_asm.S	2004-08-04 19:16:51.045914549 +0900
> @@ -0,0 +1,38 @@
...


  parent reply	other threads:[~2004-08-05 18:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05 11:05 [PATCH&RFC 2/2] OS_MCA Recovery from poisoned memory read Hidetoshi Seto
2004-08-05 12:52 ` Keith Owens
2004-08-05 18:49 ` Grant Grundler [this message]
2004-08-06 12:17 ` Hidetoshi Seto
2004-08-06 14:32 ` Keith Owens
2004-08-10  7:39 ` Hidetoshi Seto
2004-08-23  8:29 ` Christian Cotte-Barrot

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=20040805184933.GG6526@cup.hp.com \
    --to=iod00d@hp.com \
    --cc=linux-ia64@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.