From: "David S. Miller" <davem@redhat.com>
To: David Brownell <david-b@pacbell.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"Albert D. Cahalan" <acahalan@cs.uml.edu>,
Pete Zaitcev <zaitcev@redhat.com>,
johannes@erdfelt.com, rmk@arm.linux.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: pci_pool_free from IRQ
Date: Tue, 8 May 2001 17:52:45 -0700 (PDT) [thread overview]
Message-ID: <15096.38109.228916.621891@pizda.ninka.net> (raw)
In-Reply-To: <050701c0d80f$8f876ca0$6800000a@brownell.org>
In-Reply-To: <200105082108.f48L8X1154536@saturn.cs.uml.edu> <E14xFD5-0000hh-00@the-village.bc.nu> <15096.27479.707679.544048@pizda.ninka.net> <050701c0d80f$8f876ca0$6800000a@brownell.org>
David Brownell writes:
> Pete's patch to pci_pool_free() is fine with me, and I'd be glad
> to see that bit of pci interface cleaned up. Any changes needed
> other than the pci.txt doc update?
Ummm... What Alan's saying is:
1) Whatever driver is trying to shut down from IRQ context
is broken must be fixed. pci_pool is fine.
2) The Documentation/ files which suggest that such device
removal from IRQs is "OK" must be fixed because it is not
"OK" to handle device removal from IRQ context.
So Pete's change is not needed. A fix for the documentation and
broken drivers is needed instead.
Later,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-05-09 0:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-08 21:01 Pete Zaitcev
2001-05-08 21:08 ` Albert D. Cahalan
2001-05-08 21:39 ` Alan Cox
2001-05-08 21:55 ` David S. Miller
2001-05-08 22:38 ` David Brownell
2001-05-09 0:52 ` David S. Miller [this message]
2001-05-09 3:09 ` David Brownell
2001-05-09 18:30 ` Pete Zaitcev
2001-05-09 19:27 ` David S. Miller
2001-05-10 20:05 ` Pete Zaitcev
2001-05-11 17:37 ` David Brownell
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=15096.38109.228916.621891@pizda.ninka.net \
--to=davem@redhat.com \
--cc=acahalan@cs.uml.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=david-b@pacbell.net \
--cc=johannes@erdfelt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=zaitcev@redhat.com \
/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
all inboxes | Powered by JetHome®