linux-kernel - [Patch 0/4] Driver core: Some probing changes, v2

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>] [day] [month] [year] [list]

Message-ID: <20061017130551.24f2f35c@gondolin.boeblingen.de.ibm.com>
Date:	Tue, 17 Oct 2006 13:05:51 +0200
From:	Cornelia Huck <cornelia.huck@...ibm.com>
To:	Greg K-H <greg@...ah.com>
Cc:	Alan Stern <stern@...land.harvard.edu>,
	Duncan Sands <duncan.sands@...h.u-psud.fr>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: [Patch 0/4] Driver core: Some probing changes, v2

Hi,

the following patches (updated from yesterday) attempt to fix some
issues in the current device probing code:

[1/4] Don't stop probing on ->probe errors.
[2/4] Change function call order in device_bind_driver().
[3/4] Per-subsystem multithreaded probing.
[4/4] Don't fail attaching the device if it cannot be bound.

Patches 1 and 3 incorporate some comments I received (thanks to the
reviewers). Patch 4 comes out of the discussion and tries to handle
devices with and without dev->driver set more consistently.
-
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/