linux-kernel - Re: [PATCH] kaweth: use request

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: <20080531133547.10b5d7f6@core>
Date:	Sat, 31 May 2008 13:35:47 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Marcel Holtmann <marcel@...tmann.org>
Cc:	David Woodhouse <dwmw2@...radead.org>,
	Oliver Neukum <oliver@...kum.org>,
	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	Michael Zappe <zapman@...erlan.net>,
	Stephane Alnet <stephane@...icardie.fr>,
	Brad Hards <bhards@...pond.net.au>
Subject: Re: [PATCH] kaweth: use request_firmware()

> I was not late to the party. I was the first one using  
> request_firmware() and always keeping an eye on drivers using it and  
> making sure using it correctly. However drivers sneaked in without  
> that I realized it. Mainly because I don't have that hardware and  
> reviewing every single driver obviously never happened.

Nothing in the documentation says that it can't have a heirarchical name,
so naturally lots of people did it. They didn't sneak in - they improved
on the interface and evolved it. They did it in a way that didn't upset
anything else (which is why you didn't notice).

No sneaking involved.

> I repeatedly said that no hierarchical namespace should be used (and  
> this was a couple of years ago) and now since some developers misuse  
> it, it makes it right. 

It means by consensus the developer community decided that a heirarchical
namespace was useful. And that is the party you've arrived late for.

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