linux-kernel - Re: Where did find

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]

Date:	Mon, 20 Nov 2006 10:35:30 +0100
From:	"pHilipp Zabel" <philipp.zabel@...il.com>
To:	"Paul Sokolovsky" <pmiscml@...il.com>
Cc:	linux-kernel@...r.kernel.org, "Adrian Bunk" <bunk@...sta.de>,
	"Greg Kroah-Hartman" <gregkh@...e.de>, kernel-discuss@...dhelds.org
Subject: Re: Where did find_bus() go in 2.6.18?

Hi Paul,

On 11/19/06, Paul Sokolovsky <pmiscml@...il.com> wrote:
> Hello linux-kernel,
>
>   We here at Handhelds.org upgrading our drivers to 2.6.18 and I just
> caught a case of find_bus() being undefined during link.

I assume you are referring to the ipaq h2200 battery driver that uses
    bus = find_bus("w1");
to "find" the one wire bus?

I think the solution would be to use w1_bus_type instead, but for that
it would have to be exported.

Index: linux-2.6/drivers/w1/w1.c
===================================================================
--- linux-2.6.orig/drivers/w1/w1.c      2006-10-28 22:58:11.000000000 +0200
+++ linux-2.6/drivers/w1/w1.c   2006-10-29 02:01:30.000000000 +0200
@@ -194,7 +194,7 @@

 static int w1_uevent(struct device *dev, char **envp, int num_envp, char *buffe
r, int buffer_size);

-static struct bus_type w1_bus_type = {
+struct bus_type w1_bus_type = {
        .name = "w1",
        .match = w1_master_match,
        .uevent = w1_uevent,
@@ -978,3 +978,5 @@

 module_init(w1_init);
 module_exit(w1_fini);
+
+EXPORT_SYMBOL_GPL(w1_bus_type);

regards
Philipp
-
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/