linux-kernel - Re: [PATCH] leds: Move triggers before drivers in Makefile

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <alpine.LNX.1.10.0808020120290.2294@titan.stealer.net>
Date:	Sat, 2 Aug 2008 01:22:42 +0200 (CEST)
From:	Sven Wegener <sven.wegener@...aler.net>
To:	Richard Purdie <rpurdie@...ys.net>
cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] leds: Move triggers before drivers in Makefile

On Fri, 1 Aug 2008, Sven Wegener wrote:

> When both triggers and drivers are built-in, we should first register the
> triggers and then the drivers, to make default triggers work during device
> registration. We do this by moving the triggers before the drivers in the
> Makefile as init order is determined by linking order. Sadly this simple
> solution doesn't cover devices registered elsewhere in the kernel. But often
> these drivers provide their own triggers and should themselves take care of
> registering triggers before devices.
> 
> Signed-off-by: Sven Wegener <sven.wegener@...aler.net>

Ignore this one, we also attach default triggers to devices while loading 
the triggers.

Sven
--
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/