From: Jesse Barnes <jbarnes@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH/RFC]: Clean up of sn_irq_info list for PCI Hotplug
Date: Wed, 16 Mar 2005 19:34:29 +0000 [thread overview]
Message-ID: <200503161134.29905.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <42276523.3060107@sgi.com>
On Tuesday, March 15, 2005 12:32 pm, Prarit Bhargava wrote:
> I propose the following change to the sn/kernel arch SN IRQ handling.
>
> The central issue here is that the current unidirectional list
> implementation in sn_irq_info does not easily allow sn_irq_info struct
> removals when PCI devices are hotplug removed from the system.
>
> After input from a few others I changed my approach in the patch.
> Please reconsider it for submission to the community.
Patch looks ok to me, Prarit, much better than what we had (i.e. it works
during hotplug). We can continue to cleanup this file later, after you get
the hotplug driver accepted.
Jesse
prev parent reply other threads:[~2005-03-16 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 19:27 [PATCH/RFC]: Clean up of sn_irq_info list Prarit Bhargava
2005-03-03 20:07 ` Prarit Bhargava
2005-03-04 16:37 ` Prarit Bhargava
2005-03-15 20:32 ` [PATCH/RFC]: Clean up of sn_irq_info list for PCI Hotplug Prarit Bhargava
2005-03-16 19:34 ` Jesse Barnes [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=200503161134.29905.jbarnes@engr.sgi.com \
--to=jbarnes@engr.sgi.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