netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
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 16:24:07 +0800	[thread overview]
Message-ID: <1183623847.8961.45.camel@localhost.localdomain> (raw)
In-Reply-To: <1183550487.3812.14.camel@johannes.berg>

On Wed, 2007-07-04 at 14:01 +0200, Johannes Berg wrote:
> On Tue, 2007-07-03 at 15:45 -0400, Len Brown wrote:
> > Thanks for including the demo program, Rui, it works for me (tm).
> > 
> > Applied -- with the incremental patch below, which I think
> > is correct because the only caller is bus.c, which is part of
> > the base kernel, not a module.

> Are you open to reworking this on top of my multicast patches that I
> hope to get in soonish, or should I respin my multicast patches to
> ensure ACPI has a stable family and multicast group number?
> 
Hi, Johannes,

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.:)

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.

Thanks,
Rui

  reply	other threads:[~2007-07-05  8:22 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 [this message]
2007-07-05  8:35       ` Johannes Berg
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=1183623847.8961.45.camel@localhost.localdomain \
    --to=rui.zhang@intel.com \
    --cc=hadi@cyberus.ca \
    --cc=johannes@sipsolutions.net \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).