public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Belay <abelay@MIT.EDU>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-pci@atrey.karlin.mff.cuni.cz, linux-pm@lists.osdl.org,
	linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Greg KH <greg@kroah.com>
Subject: Re: [PATCH] Block on access to temporarily unavailable pci device [version 3]
Date: Thu, 19 Oct 2006 19:13:56 -0400	[thread overview]
Message-ID: <1161299636.16080.17.camel@localhost.localdomain> (raw)
In-Reply-To: <20061019154128.GD2602@parisc-linux.org>

On Thu, 2006-10-19 at 09:41 -0600, Matthew Wilcox wrote:
> Signed-off-by: Matthew Wilcox <matthew@wil.cx>

Acked-by: Adam Belay <abelay@novell.com>

It would be nice if we had sysfs expose struct file at some point... :)

Thanks,
Adam



  parent reply	other threads:[~2006-10-19 23:10 UTC|newest]

Thread overview: 23+ 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:51     ` Matthew Wilcox
2006-10-18 15:52       ` Alan Stern
2006-10-18 16:05         ` Alan Cox
2006-10-18 16:09           ` Matthew Wilcox
2006-10-18 16:42             ` 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:27         ` Nick Piggin
2006-10-18 15:50     ` Alan Cox
2006-10-18 16:20       ` Matthew Wilcox
2006-10-18 16:39         ` Alan Cox
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 [this message]
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=1161299636.16080.17.camel@localhost.localdomain \
    --to=abelay@mit.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=linux-pm@lists.osdl.org \
    --cc=matthew@wil.cx \
    /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