All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Tejun Heo <htejun@gmail.com>,
	linux-ide@vger.kernel.org, Jeff Garzik <jeff@garzik.org>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fixups to ATA ACPI hotplug
Date: Tue, 20 May 2008 15:00:59 +0100	[thread overview]
Message-ID: <20080520140059.GA6471@srcf.ucam.org> (raw)
In-Reply-To: <20080520135828.GA3167@homac>

On Tue, May 20, 2008 at 03:58:30PM +0200, Holger Macht wrote:

> Handle bay devices in dock stations
> 
> * Differentiate between bay devices in dock stations and others:
> 
>  - When an ACPI_NOTIFY_EJECT_REQUEST appears, just signal uevent to
>    userspace (that is when the optional eject button on a bay device is
>    pressed/pulled) giving the possibility to unmount file systems and to
>    clean up. Also, only send uevent in case we get an EJECT_REQUEST
>    without doing anything else. In other cases, you'll get an add/remove
>    event because libata attaches/detaches the device.
> 
>  - In case of a dock event, which in turn signals an
>    ACPI_NOTIFY_EJECT_REQUEST, immediately detach the device, because it
>    may already have been gone
> 
> * In case of an ACPI_NOTIFY_DEVICE/BUS_CHECK, evaluate _STA to check if
>   the device has been plugged or unplugged. If plugged, hotplug it, if
>   unplugged, just signal event to userspace
>   (initial patch by Matthew Garrett <mjg59@srcf.ucam.org>)
> 
> Signed-off-by: Holger Macht <hmacht@suse.de>

As long as this fixes the hang on dock removal, this looks good to me.

Acked-by: Matthew Garrett <mjg@redhat.com>
-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2008-05-20 14:01 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-05 22:33 2.6.25 semantic change in bay handling? Matthew Garrett
2008-05-06  8:13 ` Holger Macht
2008-05-06  8:21   ` Matthew Garrett
2008-05-06  8:40     ` Tejun Heo
2008-05-06  8:46       ` Matthew Garrett
2008-05-06  8:53         ` Tejun Heo
2008-05-06  9:17           ` Matthew Garrett
2008-05-06 11:21             ` Holger Macht
2008-05-06 11:31               ` Matthew Garrett
2008-05-06 17:27             ` Holger Macht
2008-05-06 17:48               ` Matthew Garrett
2008-05-06 18:36             ` Holger Macht
2008-05-06 18:48               ` Matthew Garrett
2008-05-06 22:06                 ` Holger Macht
2008-05-06  9:29         ` Holger Macht
2008-05-06  9:39           ` Matthew Garrett
2008-05-06  9:26       ` Holger Macht
2008-05-06  9:36         ` Matthew Garrett
2008-05-19 16:29           ` [PATCH] Fixups to ATA ACPI hotplug Matthew Garrett
2008-05-20  7:44             ` Holger Macht
2008-05-20 10:20               ` Matthew Garrett
2008-05-20 13:18                 ` Holger Macht
2008-05-20 13:22                   ` Matthew Garrett
2008-05-20 13:58                     ` Holger Macht
2008-05-20 14:00                       ` Matthew Garrett [this message]
2008-05-21 22:26                       ` Andrew Morton
2008-05-20  8:49             ` Holger Macht
2008-05-06  8:40   ` 2.6.25 semantic change in bay handling? Holger Macht

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=20080520140059.GA6471@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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 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.