linux-kernel - Re: [PATCH 2/3] firmware: Add CONFIG_BUILTIN

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

Message-Id: <7BD202F0-0E0E-495D-93CA-45F2E5AA8065@holtmann.org>
Date:	Sun, 25 May 2008 20:15:13 +0200
From:	Marcel Holtmann <marcel@...tmann.org>
To:	Michael Buesch <mb@...sch.de>
Cc:	Johannes Berg <johannes@...solutions.net>,
	David Woodhouse <dwmw2@...radead.org>,
	Sam Ravnborg <sam@...nborg.org>, linux-kernel@...r.kernel.org,
	aoliva@...hat.com, alan@...rguk.ukuu.org.uk,
	Abhay Salunke <Abhay_Salunke@...l.com>, kay.sievers@...y.org,
	Takashi Iwai <tiwai@...e.de>
Subject: Re: [PATCH 2/3] firmware: Add CONFIG_BUILTIN_FIRMWARE option

Hi Michael,

>> this should all be done in userspace and not inside the kernel.  
>> Export
>> the special device versions via struct device and stop being lazy.
>
> No. Wait. It's not exactly going to work this way.
> You're not going to break my ABI and then tell me I'm going to work  
> around
> that, right? Answer: No.
>
> b43 will use the slash in request_firmware. That is not going to  
> change.
>
> This is _exactly_ what users are so tired about. Every now and then  
> people
> decide to change some ABI.

don't give me that crap. Nobody plans to break everything just right  
now and leave people hanging in between. We will do a smooth  
transition. Your users won't even notice it.

And we change the API/ABI all the time. Get used to it.

Regards

Marcel

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