netdev - Re: [PATCH] ACPI: export acpi events via generic netlink

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 05 Jul 2007 16:24:07 +0800
From:	Zhang Rui <rui.zhang@...el.com>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	Len Brown <lenb@...nel.org>,
	"linux-acpi@...r" <linux-acpi@...r.kernel.org>,
	netdev@...r.kernel.org, hadi@...erus.ca
Subject: Re: [PATCH] ACPI: export acpi events via generic netlink

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
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html