From: "Sourav Sen" <souravs-hAGStUev6lJWk0Htik3J/w@public.gmane.org>
To: "HELGAAS,BJORN (HP-Ft. Collins)"
<bjorn_helgaas-+0+VdgW1APZVd2G1PmaOdg@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"MOSBERGER,DAVID (HP-PaloAlto,unix3)"
<davidm-sDzT885Ts8HQT0dZR+AlfA@public.gmane.org>,
Andi Kleen <ak-l3A5Bk7waGM@public.gmane.org>,
Jun Nakajima
<jun.nakajima-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
linux-ia64-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: [PATCH] ACPI PCI IRQ routing rework
Date: Tue, 18 May 2004 10:09:29 +0530 [thread overview]
Message-ID: <016701c43c92$1c521650$39624c0f@india.hp.com> (raw)
In-Reply-To: <200405170857.55814.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
+ Or are you saying that my patch introduces a new panic situation
+ that didn't exist before?
No, I am not saying that. I was referring to the same old panic in
assign_irq_vector().
--Sourav
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
next prev parent reply other threads:[~2004-05-18 4:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A11077E28200D51182EA00D0B77552530E8A8522@xin02.india.hp.com>
2004-05-17 14:57 ` [PATCH] ACPI PCI IRQ routing rework Bjorn Helgaas
[not found] ` <200405170857.55814.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2004-05-18 4:39 ` Sourav Sen [this message]
2004-05-15 17:20 Bjorn Helgaas
[not found] ` <200405151120.45753.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2004-05-15 20:23 ` Bjorn Helgaas
2004-05-17 10:09 ` Sourav Sen
2004-05-17 15:41 ` Andi Kleen
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='016701c43c92$1c521650$39624c0f@india.hp.com' \
--to=souravs-hagstuev6ljwk0htik3j/w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ak-l3A5Bk7waGM@public.gmane.org \
--cc=bjorn_helgaas-+0+VdgW1APZVd2G1PmaOdg@public.gmane.org \
--cc=davidm-sDzT885Ts8HQT0dZR+AlfA@public.gmane.org \
--cc=jun.nakajima-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-ia64-u79uwXL29TY76Z2rM5mHXA@public.gmane.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