From: Matthew Wilcox <matthew@wil.cx>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Brian King <brking@us.ibm.com>,
linux-pci@atrey.karlin.mff.cuni.cz, linux-pm@lists.osdl.org,
linux-kernel@vger.kernel.org, Adam Belay <abelay@MIT.EDU>
Subject: Re: [linux-pm] [PATCH] Block on access to temporarily unavailable pci device
Date: Wed, 18 Oct 2006 10:09:26 -0600 [thread overview]
Message-ID: <20061018160926.GS22289@parisc-linux.org> (raw)
In-Reply-To: <1161187503.9363.75.camel@localhost.localdomain>
On Wed, Oct 18, 2006 at 05:05:02PM +0100, Alan Cox wrote:
> If the user specified O_NDELAY then -EWOULDBLOCK not wait
sysfs doesn't give us the struct file, so we can't tell.
next prev parent reply other threads:[~2006-10-18 16:09 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 14:51 [PATCH] Block on access to temporarily unavailable pci device Matthew Wilcox
2006-10-17 14:54 ` Matthew Wilcox
2006-10-17 21:25 ` Brian King
2006-10-18 14:38 ` [linux-pm] " Alan Stern
2006-10-18 14:38 ` Alan Stern
2006-10-18 14:51 ` Matthew Wilcox
2006-10-18 14:51 ` [linux-pm] " Matthew Wilcox
2006-10-18 15:52 ` Alan Stern
2006-10-18 15:52 ` Alan Stern
2006-10-18 16:05 ` Alan Cox
2006-10-18 16:05 ` [linux-pm] " Alan Cox
2006-10-18 16:09 ` Matthew Wilcox [this message]
2006-10-18 16:42 ` Alan Cox
2006-10-18 16:42 ` [linux-pm] " Alan Cox
2006-10-18 14:51 ` Matthew Wilcox
2006-10-18 14:57 ` Matthew Wilcox
2006-10-18 15:12 ` Nick Piggin
2006-10-18 15:16 ` Matthew Wilcox
2006-10-18 15:16 ` Matthew Wilcox
2006-10-18 15:27 ` Nick Piggin
2006-10-18 15:27 ` Nick Piggin
2006-10-18 15:50 ` Alan Cox
2006-10-18 15:50 ` Alan Cox
2006-10-18 16:20 ` Matthew Wilcox
2006-10-18 16:39 ` Alan Cox
2006-10-18 16:39 ` Alan Cox
2006-10-18 17:14 ` Matthew Wilcox
2006-10-18 17:14 ` Matthew Wilcox
2006-10-19 15:41 ` [PATCH] Block on access to temporarily unavailable pci device [version 3] Matthew Wilcox
2006-10-19 16:32 ` Alan Cox
2006-10-19 23:13 ` Adam Belay
2006-10-19 23:51 ` Greg KH
2006-10-19 23:51 ` Greg KH
2006-10-20 21:50 ` Brian King
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=20061018160926.GS22289@parisc-linux.org \
--to=matthew@wil.cx \
--cc=abelay@MIT.EDU \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=brking@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linux-pm@lists.osdl.org \
--cc=stern@rowland.harvard.edu \
/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.