linux-kernel - Re: [PATCH] lirc: remove backwards compatibility macro obfuscation (Was: Free Linux Driver Development!)

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]

Date:	Fri, 02 Feb 2007 13:51:35 +0100
From:	Jan Dittmer <jdi@....org>
To:	Pekka Enberg <penberg@...helsinki.fi>
CC:	lirc@...telmus.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] lirc: remove backwards compatibility macro obfuscation
 (Was: Free Linux Driver Development!)

Pekka Enberg wrote:
> On 2/2/07, Jan Dittmer <jdi@....org> wrote:
>> Pekka, it would be better if you could sort out most of the
>> basic issues with lirc directly with the developers of lirc
>> and then prepare a complete patch series and post that to
>> lkml. Incrementally adding one driver after another. Posting
>> patches to non-existent sources to lkml is pointless. First
>> create a discussion base, please.
> 
> What discussion base? You need to get rid of the cruft anyway and now
> you have patch to do that. I am not volunteering to sort out _all_ the
> issues.

I really really welcome your efforts - no doubt.

I wanted to express that the patches you posted are simply not
suitable for lkml discussion as there was no full patchset for
lirc for review posted, prior to your patches.

Normal process for new features (and lirc is a new feature so
far lkml is concerned) is like (as I understand it):
  1. post full patchset
  2. duck
  3. receive criticism & patches
  4. integrate results from 3
  5. goto 1
You started at 3. It would be better to start with the whole
picture at 1.

I hope I made myself clearer now.

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