linux-kernel - Re: [PATCH] firmware: Allocate firmware id dynamically

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: <20090527150435.GA31097@kroah.com>
Date:	Wed, 27 May 2009 08:04:35 -0700
From:	Greg KH <greg@...ah.com>
To:	Kay Sievers <kay.sievers@...y.org>
Cc:	Samuel Ortiz <sameo@...ux.intel.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Andrew Morton <akpm@...ux-foundation.org>,
	holtmann@...ux.intel.com, yi.zhu@...el.com,
	linux-kernel@...r.kernel.org, linville@...driver.com
Subject: Re: [PATCH] firmware: Allocate firmware id dynamically

On Wed, May 27, 2009 at 10:30:19AM +0200, Kay Sievers wrote:
> On Wed, May 27, 2009 at 10:17, Samuel Ortiz <sameo@...ux.intel.com> wrote:
> 
> >> next-20090526:samples/firmware_class/firmware_sample_firmware_class.c
> > Do I really need to fix this one too ?
> 
> I does not compile since ages, it is totally outdated and uses the
> long removed struct class_device. And we really don't need an example
> for firmware loading, I think. This file should just be deleted.

Yeah, I had plans to write it "properly", but it's at the end of my long
TODO list :(

I'll just go delete the thing instead.

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/