From: Jeff Garzik <jgarzik@pobox.com>
To: Martin Diehl <lists@mdiehl.de>
Cc: jt@hpl.hp.com, Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.5 IrDA] vlsi driver update
Date: Sun, 17 Aug 2003 15:38:43 -0400 [thread overview]
Message-ID: <3F3FD9C3.6000601@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0308172017160.1469-100000@notebook.home.mdiehl.de>
Martin Diehl wrote:
> On Sun, 17 Aug 2003, Jeff Garzik wrote:
>
>
>>Jean Tourrilhes wrote:
>>
>>>ir2603_vlsi-05.diff :
>>>~~~~~~~~~~~~~~~~~~~
>>> <Patch from Martin Diehl>
>>
>>this patch needs splitting up
> 1) apply single big patch, basically replacing the code
> 2) back out the existing driver and put in a new one resulting in the same
> code as above
> 3) do nothing, i.e. stay with vlsi_ir being worse and unsupported in 2.4
> forever
>
> Please advise!
4) split up the patch, pretty please with sugar on it.
Jeff
next prev parent reply other threads:[~2003-08-17 19:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-11 21:03 [PATCH 2.5 IrDA] vlsi driver update Jean Tourrilhes
2003-08-17 16:43 ` Jeff Garzik
2003-08-17 19:14 ` Martin Diehl
2003-08-17 19:38 ` Jeff Garzik [this message]
2003-08-18 8:55 ` Martin Diehl
-- strict thread matches above, loose matches on Subject: below --
2003-08-08 18:54 Jean Tourrilhes
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=3F3FD9C3.6000601@pobox.com \
--to=jgarzik@pobox.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@mdiehl.de \
/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;
as well as URLs for NNTP newsgroup(s).