From: Yu Luming <luming.yu@intel.com>
To: Dmitry Torokhov <dtor@insightbb.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>, linux-acpi@vger.kernel.org
Subject: Re: acpi button event to input layer (was [RFC] [PATCH] Make ACPI button driver an input device)
Date: Tue, 5 Sep 2006 16:15:56 +0800 [thread overview]
Message-ID: <200609051615.56245.luming.yu@intel.com> (raw)
In-Reply-To: <200608302257.25382.dtor@insightbb.com>
On Thursday 31 August 2006 10:57, Dmitry Torokhov wrote:
> On Monday 28 August 2006 03:06, Yu Luming wrote:
> > Matthew / Dmitry,
> >
> > I recall there was a patch to make acpi button driver as input device.
> > Do you have any update patch? Because we want to transition acpi event
> > mechanism from /proc/acpi/event to input layer. I guess the acpi button
> > driver would be the first one to complete such transition.
> >
> > http://www.gatago.com/linux/kernel/11320641.html
>
> I sent the following patch to Len some time ago. It needs the attached
> cleanup patch.
Hi Dmitry,
The patch doesn't apply. It is somehow changed by email client or server.
And, I got :
patching file drivers/acpi/button.c
patch: **** malformed patch at line 4: #include <linux/types.h>
Could you please send the patch as attachment to me.
--
Thanks,
Luming
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-09-05 8:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 7:06 acpi button event to input layer (was [RFC] [PATCH] Make ACPI button driver an input device) Yu Luming
2006-08-31 2:57 ` Dmitry Torokhov
2006-09-05 8:15 ` Yu Luming [this message]
2006-09-06 5:15 ` Dmitry Torokhov
[not found] ` <200609061733.58222.luming.yu@intel.com>
2006-09-06 12:43 ` Dmitry Torokhov
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=200609051615.56245.luming.yu@intel.com \
--to=luming.yu@intel.com \
--cc=dtor@insightbb.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.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.