From: Johannes Berg <johannes@sipsolutions.net>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Len Brown <lenb@kernel.org>,
"linux-acpi@vger" <linux-acpi@vger.kernel.org>,
netdev@vger.kernel.org, hadi@cyberus.ca
Subject: Re: [PATCH] ACPI: export acpi events via generic netlink
Date: Thu, 05 Jul 2007 10:35:41 +0200 [thread overview]
Message-ID: <1183624541.3818.2.camel@johannes.berg> (raw)
In-Reply-To: <1183623847.8961.45.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
On Thu, 2007-07-05 at 16:24 +0800, Zhang Rui wrote:
> I missed the discussion about the multicast issues.
> You don't need to reserve a family and group ID for ACPI. I'll rework
> this on your patches.:)
I don't want to hold you, don't worry, I can handle it as well.
> But I don't know when these mutlicast patches can be merged while I hope
> the function of exporting ACPI event via genetlink can be added ASAP.
>
> I'm okay to hold off on this patch if you think the multicast patches
> can be merged soon. Or else I tend to apply it first and send an
> additional patch together with your patches later.
I personally think it's ready to go and haven't received any further
comments, but maybe something will come up still. I'll wait a few days
and then repost as an actual .23 submission.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2007-07-05 8:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 3:40 [PATCH] ACPI: export acpi events via generic netlink Zhang Rui
2007-07-03 17:18 ` Johannes Berg
2007-07-03 19:45 ` Len Brown
2007-07-04 12:01 ` Johannes Berg
2007-07-05 8:24 ` Zhang Rui
2007-07-05 8:35 ` Johannes Berg [this message]
2007-07-05 8:54 ` Zhang Rui
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=1183624541.3818.2.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=hadi@cyberus.ca \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox