From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] 2.4.25-pre8, 2.6.2-rc2 mca.c - pass irq_safe around
Date: Tue, 10 Feb 2004 22:57:17 +0000 [thread overview]
Message-ID: <16425.25037.798727.698612@napali.hpl.hp.com> (raw)
In-Reply-To: <9337.1076049423@kao2.melbourne.sgi.com>
>>>>> On Fri, 06 Feb 2004 17:37:03 +1100, Keith Owens <kaos@sgi.com> said:
Keith> The patch is against 2.4.25-pre8 bk. It also applies to
Keith> 2.6.2-rc2 bk (with some fuzz and offsets), after applying my
Keith> previous 6 patches to 2.6.2-rc2 mca.c.
Keith> Patches from Ben Woodward to calculate irq_safe once and pass
Keith> it around.
I applied the patch but I'm wondering what happens if someone adds a
new SAL_INFO_TYPE which isn't irq-safe. Wouldn't it be safer to flip
things around and check sal_info_type against known-to-be-safe values?
--david
next prev parent reply other threads:[~2004-02-10 22:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 6:37 [patch] 2.4.25-pre8, 2.6.2-rc2 mca.c - pass irq_safe around Keith Owens
2004-02-10 22:57 ` David Mosberger [this message]
2004-02-10 23:05 ` Keith Owens
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=16425.25037.798727.698612@napali.hpl.hp.com \
--to=davidm@napali.hpl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox