linux-kernel - Re: [PATCH] Driver core: export platform_device_register

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, 21 Dec 2009 09:14:45 -0800
From:	Greg KH <gregkh@...e.de>
To:	Mike Frysinger <vapier.adi@...il.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	Michael Hennerich <michael.hennerich@...log.com>
Subject: Re: [PATCH] Driver core: export platform_device_register_data as a
 GPL symbol

On Mon, Dec 21, 2009 at 12:05:40PM -0500, Mike Frysinger wrote:
> On Mon, Dec 21, 2009 at 11:46, Greg KH wrote:
> > On Mon, Dec 21, 2009 at 11:41:08AM -0500, Mike Frysinger wrote:
> >> This allows MFD's to register/bind drivers for their sub devices while
> >> still being compiled as a module.
> >
> > Is this a problem that we need to get resolved in .33, or older kernels,
> > or just for .34?
> 
> the functionality is in place now, so it could be used in .33.  but it
> isnt that big of a deal to simply say the mfd core cant be built as a
> module right now.
> 
> so, it'd be nice for .33, but if it's too much hassle, .34 is OK.

Ok, I'll queue it up for .33, as it keeps an in-kernel driver from
working properly now.

thanks,

greg k-h
--
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/