From: Len Brown <lenb@kernel.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Zhang Rui <rui.zhang@intel.com>,
linux-acpi@vger.kernel.org, astarikovskiy@suse.de
Subject: Re: [PATCH] ACPI: don't send netlink events for those that go into input layer
Date: Thu, 23 Aug 2007 22:18:38 -0400 [thread overview]
Message-ID: <200708232218.38568.lenb@kernel.org> (raw)
In-Reply-To: <20070823212255.GB17191@khazad-dum.debian.net>
On Thursday 23 August 2007 17:22, Henrique de Moraes Holschuh wrote:
> Hi Len!
>
> On Thu, 23 Aug 2007, Len Brown wrote:
>
> > I like it, Rui.
> >
> > I think that upon this patch, we can start to deprecate acpi_bus_generate_event,
> > as every user of it is now handled by the input layer or netlink.
> >
> > applied.
>
> This calls for (good!) changes in thinkpad-acpi and some issues I had with
> exactly the same problem.
>
> Len, to which tree is that change targeted? I will have to target some
> thinkpad-acpi changes that depend on it.
Since Rui's patch is an incremental to netlink events,
which are new in 2.6.23, I'm going to request Rui's patch
for inclusion in 2.6.23. I'm also going to include
"[PATCH] ACPI: Schedule /proc/acpi/event for removal"
with it.
They'll both be in the acpi-test tree upon my next push,
probably tonight. maybe go to Linus as soon as tomorrow
since delay in the -rc3 timeframe would be folly.
thanks,
-Len
next prev parent reply other threads:[~2007-08-24 2:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 17:24 [PATCH] ACPI: don't send netlink events for those that go into input layer Zhang Rui
2007-08-23 18:30 ` Len Brown
2007-08-23 21:22 ` Henrique de Moraes Holschuh
2007-08-24 2:18 ` Len Brown [this message]
2007-08-25 5:18 ` Henrique de Moraes Holschuh
2007-08-23 19:13 ` [PATCH] ACPI: Schedule /proc/acpi/event for removal Len Brown
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=200708232218.38568.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=astarikovskiy@suse.de \
--cc=hmh@hmh.eng.br \
--cc=linux-acpi@vger.kernel.org \
--cc=rui.zhang@intel.com \
/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.