linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Flameeyes <dgp85@users.sourceforge.net>
To: LKML <linux-kernel@vger.kernel.org>,
	LIRC list <lirc-list@lists.sourceforge.net>
Subject: [PATCH] lirc for 2.5/2.6 kernels - 20030802
Date: 02 Aug 2003 12:39:11 +0200	[thread overview]
Message-ID: <1059820741.3116.24.camel@laurelin> (raw)

Hi,
This is the fourth version of my patch for use LIRC drivers under
2.5/2.6 kernels.

As usual, you can find it at
http://flameeyes.web.ctonet.it/lirc/patch-lirc-20030802.diff.bz2

I changed the naming scheme, because I tried and the patch applies also
in earliers and (probably) futures kernels, and call it only
"patch-lirc.diff" will confuse about the versions. I think a datestamp
is the best choice for now.

This version includes minor changes, but an important one, Koos Vriezen
sent me another fixes for lirc_serial driver (thanks, at the moment I
haven't a serial device, and the electronic shops are closed, so I can't
test it directly).
Also I removed the .Makefile.swp present in the last patch (I forgot to
close KVim before do the diff).

This is also the first patch I post to the official lirc mailing list,
HTH other lirc users that want to pass to 2.5/2.6 kernels.

-- 
Flameeyes <dgp85@users.sf.net>


             reply	other threads:[~2003-08-02 10:38 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-02 10:39 Flameeyes [this message]
2003-08-07 21:43 ` [PATCH] lirc for 2.5/2.6 kernels - 20030802 Pavel Machek
2003-08-08  9:21   ` Flameeyes
2003-08-08 23:17     ` Pavel Machek
2003-08-09 14:46       ` Christoph Bartelmus
2003-08-11 12:47         ` Pavel Machek
2003-08-11 13:11           ` Flameeyes
2003-08-11 14:42             ` Herbert Pötzl
2003-08-11 15:41               ` Pavel Machek
2003-08-11 18:40               ` Gerd Knorr
2003-08-11 15:38             ` Pavel Machek
2003-08-11 15:48               ` Flameeyes
2003-08-11 16:39                 ` Gerd Knorr
2003-08-11 17:56                   ` Johannes Stezenbach
2003-08-11 18:55                     ` Pavel Machek
2003-08-11 18:59                     ` Vojtech Pavlik
2003-08-11 19:17                       ` Pavel Machek
2003-08-11 19:34                         ` Vojtech Pavlik
2003-08-11 19:55                           ` Pavel Machek
2003-08-11 19:59                           ` Valdis.Kletnieks
2003-08-11 20:13                             ` Vojtech Pavlik
2003-08-11 19:22                       ` Pavel Machek
2003-08-14 15:22                   ` Dennis Björklund
2003-08-14 16:06                     ` Gerd Knorr
2003-08-11 18:52                 ` Pavel Machek
2003-08-11 20:01                   ` Flameeyes
2003-08-11 17:35               ` Johannes Stezenbach
2003-08-11 18:57                 ` Pavel Machek
2003-08-11 18:31           ` Gerd Knorr
2003-08-11 18:59             ` Pavel Machek
2003-08-11 19:54               ` Gerd Knorr
2003-08-11 20:04                 ` Pavel Machek
2003-08-11 13:14         ` Pavel Machek
2003-08-09 19:15   ` Flameeyes
2003-08-11 11:10   ` Pavel Machek

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=1059820741.3116.24.camel@laurelin \
    --to=dgp85@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lirc-list@lists.sourceforge.net \
    /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).