linux-kernel - Re: [RFC PATCH] Multi-threaded device probing

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: <200607270202.00854.arnd@arndb.de>
Date:	Thu, 27 Jul 2006 02:02:00 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Greg KH <gregkh@...e.de>
Cc:	linux-kernel@...r.kernel.org, greg@...ah.com
Subject: Re: [RFC PATCH] Multi-threaded device probing

On Tuesday 25 July 2006 22:30, Greg KH wrote:
> --- gregkh-2.6.orig/include/linux/device.h
> +++ gregkh-2.6/include/linux/device.h
> @@ -105,6 +105,8 @@ struct device_driver {
>         void    (*shutdown)     (struct device * dev);
>         int     (*suspend)      (struct device * dev, pm_message_t state);
>         int     (*resume)       (struct device * dev);
> +
> +       unsigned int multithread_probe:1;
>  };
>  

Why use a bit field here? It ends up consuming sizeof(long) anyway
and causes more complex code, with no obvious benefit.

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