public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Dittmer <jdi@l4x.org>
To: Pekka J Enberg <penberg@cs.helsinki.fi>
Cc: lirc@bartelmus.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lirc: remove backwards compatibility macro obfuscation (Was: Free Linux Driver Development!)
Date: Fri, 02 Feb 2007 12:10:17 +0100	[thread overview]
Message-ID: <45C31C19.5040200@l4x.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0702021038270.21422@sbz-30.cs.Helsinki.FI>

Pekka J Enberg wrote:
> From: Pekka Enberg <penberg@cs.helsinki.fi>
> 
> On 02 Feb 2007 05:54:00 +0100, Christoph Bartelmus <lirc@bartelmus.de> wrote:
>> I just made clear that I don't have the time to do the merging of LIRC
>> drivers to the kernel myself. In fact a lot of work still needs to be
>> done before LIRC drivers are ready to be included into the kernel.
> 
> [snip]
> 
> On 02 Feb 2007 05:54:00 +0100, Christoph Bartelmus <lirc@bartelmus.de> wrote:
>> Any help welcome.
> 
> Here's a start. You really should run Lindent on the sources too.

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.

> Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi>
> ---
> 
>  drivers/lirc_atiusb/lirc_atiusb.c           |  102 -----------------
>  drivers/lirc_bt829/lirc_bt829.c             |    9 -

You might want to fix the directory structure first and check
which drivers already exist in-tree.
Also, as Vincent noted, most drivers have to be converted
to use the input layer first.

Jan

  parent reply	other threads:[~2007-02-02 11:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-02  8:39 [PATCH] lirc: remove backwards compatibility macro obfuscation (Was: Free Linux Driver Development!) Pekka J Enberg
2007-02-02 11:04 ` Vincent Vanackere
2007-02-04  3:04   ` [PATCH] lirc: remove backwards compatibility macro obfuscation Christoph Bartelmus
2007-02-02 11:10 ` Jan Dittmer [this message]
2007-02-02 11:32   ` [PATCH] lirc: remove backwards compatibility macro obfuscation (Was: Free Linux Driver Development!) Pekka Enberg
2007-02-02 12:51     ` Jan Dittmer
2007-02-04  3:03 ` [PATCH] lirc: remove backwards compatibility macro obfuscation Christoph Bartelmus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45C31C19.5040200@l4x.org \
    --to=jdi@l4x.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lirc@bartelmus.de \
    --cc=penberg@cs.helsinki.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox