linux-kernel - Re: [PATCH v3 1/4] ACPI: Support system notify handler via .sys

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

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

Message-ID: <1353957902.26955.133.camel@misato.fc.hp.com>
Date:	Mon, 26 Nov 2012 12:25:02 -0700
From:	Toshi Kani <toshi.kani@...com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	linux-acpi@...r.kernel.org, lenb@...nel.org,
	linux-kernel@...r.kernel.org, bhelgaas@...gle.com,
	isimatu.yasuaki@...fujitsu.com, liuj97@...il.com
Subject: Re: [PATCH v3 1/4] ACPI: Support system notify handler via
 .sys_notify

> > >  {
> > > -	struct acpi_device *device = NULL;
> > > -	struct acpi_driver *driver;
> > > -
> > >  	ACPI_DEBUG_PRINT((ACPI_DB_INFO, "Notification %#02x to handle %p\n",
> > >  			  type, handle));
> > >  
> > > -	blocking_notifier_call_chain(&acpi_bus_notify_list,
> > > -		type, (void *)handle);
> 
> By the way, there is exacly one user of this chain, which is dock.c.
> 
> What about convering that to something different and dropping the chain to
> start with?

I agree.  I will look further to see what interface we can use to
replace it.

Thanks,
-Toshi

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/