mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Jens David <dg1kjd@afthd.tu-darmstadt.de>
Cc: marcelo.tosatti@cyclades.com, linux-kernel@vger.kernel.org,
	davem@redhat.com, jgarzik@pobox.com
Subject: Re: [SPAM?] [PATCH] Backport via-ircc to Linux-2.4 from 2.6
Date: Wed, 14 Jan 2004 11:56:16 -0800	[thread overview]
Message-ID: <20040114195616.GB21754@bougret.hpl.hp.com> (raw)
In-Reply-To: <200401140817.i0E8HBw27502@dl0td.afthd.tu-darmstadt.de>

On Wed, Jan 14, 2004 at 09:17:11AM +0100, Jens David wrote:
> Hi,
> 
> look, I do not have much time for this political discussion.
> All I say is:
> 
> - I backported the VIA FIR IRDA driver from 2.6 because I needed it
> - Most other AMD-based laptop users will need it too
> - The driver (or at least a close relative) worked flawlessly for me for 1 year
> - The backport does not affect other drivers or system stability even when loaded
> - I am willing to maintain it till 2.4 is phased out. Which is the case when
>   distros decide to go 2.6, but no earlier.
> 
> Here is the patch, take it or leave it or start talking CODE.
> 
>   -- j

	Wow, whose code are we talking about ? Just for your
information (and Jeff will confirm), it was possible to integrate the
VIA driver in the kernel only because I fixed many integration issues,
(VIA was mostly unresponsive), and I don't have this hardware.
	I told you the problem was the lack of testing. Now that you
solved this issue, things will go forward. But, I'm only human.

	Jean

  reply	other threads:[~2004-01-14 19:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040114002920.GA13260@bougret.hpl.hp.com>
2004-01-14  8:17 ` Jens David
2004-01-14 19:56   ` Jean Tourrilhes [this message]
2004-01-15  2:31   ` Jean Tourrilhes
2004-01-13 22:43 Jens David

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=20040114195616.GB21754@bougret.hpl.hp.com \
    --to=jt@bougret.hpl.hp.com \
    --cc=davem@redhat.com \
    --cc=dg1kjd@afthd.tu-darmstadt.de \
    --cc=jgarzik@pobox.com \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    /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

all inboxes | Powered by JetHome®