From: Len Brown <lenb@kernel.org>
To: akpm@linux-foundation.org
Cc: linux-acpi@vger.kernel.org, marvin@mydatex.cz, hmacht@suse.de,
rui.zhang@intel.com, shaohua.li@intel.com, stable@kernel.org
Subject: Re: [patch 6/6] acpi dock: terminate eject request is the dock is not present
Date: Fri, 09 Jan 2009 16:09:49 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0901091607200.16697@localhost.localdomain> (raw)
In-Reply-To: <200901092017.n09KHEqd015005@imap1.linux-foundation.org>
The bug report suggest that this patch is not a complete fix for the
issue, so I'd prefer we get a resolution, or at least a better
understanding of the failure, before sending patches upstream
for this issue.
thanks
Len Brown, Intel Open Source Technology Center
On Fri, 9 Jan 2009, akpm@linux-foundation.org wrote:
> From: Daniel Smolik <marvin@mydatex.cz>
>
> Taken from http://bugzilla.kernel.org/show_bug.cgi?id=12360
>
> nfi if it's right - I merged it so it wouldn't get lost.
>
> Cc: Zhang Rui <rui.zhang@intel.com>
> Cc: Len Brown <lenb@kernel.org>
> Cc: "Li, Shaohua" <shaohua.li@intel.com>
> Cc: <hmacht@suse.de>
> Cc: <stable@kernel.org> [2.6.26.x, 2.6.27.x, 2.6.28.x]
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> drivers/acpi/dock.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff -puN drivers/acpi/dock.c~acpi-dock-terminate-eject-request-is-the-dock-is-not-present drivers/acpi/dock.c
> --- a/drivers/acpi/dock.c~acpi-dock-terminate-eject-request-is-the-dock-is-not-present
> +++ a/drivers/acpi/dock.c
> @@ -668,6 +668,9 @@ EXPORT_SYMBOL_GPL(unregister_hotplug_doc
> */
> static int handle_eject_request(struct dock_station *ds, u32 event)
> {
> + if (!dock_present(ds))
> + return -ENODEV;
> +
> if (dock_in_progress(ds))
> return -EBUSY;
>
> _
>
next prev parent reply other threads:[~2009-01-09 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 20:17 [patch 6/6] acpi dock: terminate eject request is the dock is not present akpm
2009-01-09 21:09 ` Len Brown [this message]
2009-01-10 7:42 ` Daniel Smolik
2009-01-11 16:14 ` 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=alpine.LFD.2.00.0901091607200.16697@localhost.localdomain \
--to=lenb@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hmacht@suse.de \
--cc=linux-acpi@vger.kernel.org \
--cc=marvin@mydatex.cz \
--cc=rui.zhang@intel.com \
--cc=shaohua.li@intel.com \
--cc=stable@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