linux-kernel - Re: [PATCH] HID: Add NOGET quirk for the CH Pro Throttle

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: <4D9ED443.6040206@vexillium.org>
Date:	Fri, 08 Apr 2011 10:24:19 +0100
From:	Unavowed <unavowed@...illium.org>
To:	Jiri Kosina <jkosina@...e.cz>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] HID: Add NOGET quirk for the CH Pro Throttle

On 06/04/11 15:17, Jiri Kosina wrote:
>> I, and probably other flight sim fans running Linux, would be very happy
>> if someone could fix write a patch fixing this.
> 
> I thought you'd figure that out :) Thanks for the report, I have queued 
> the fix in my tree.

Great, thanks.

>> And if I may comment on that "no pseudonyms" policy, I don't fully
>> understand the motivation behind it.  After all, there have been many
>> authors of copyrighted works who created them without revealing their
>> real name[1].  Is this something to please the lawyers of Linux's
>> corporate overlords?
> 
> I guess this would be topic for a separate thread, but anyway ... but I 
> believe you'd be able to dig much information from reading the threads 
> where entity calling itself 'Shem Multinymous' tried to submit Thinkpad 
> Embedded Controller drivers.
> 
> It basically defeats the Developer's Certificate of Origin process 
> completely.

Thanks for the reference, I'll remember it the next time I consider
writing a patch.
-- 
Unavowed
--
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/