Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Jarmo <oh1mrr@nic.fi>
Cc: linux-hams@vger.kernel.org
Subject: Re: Timers in 2.6.x kernels
Date: Mon, 15 Mar 2004 14:38:25 +0100	[thread overview]
Message-ID: <20040315133825.GA3483@linux-mips.org> (raw)
In-Reply-To: <200403150806.46071.oh1mrr@nic.fi>

On Mon, Mar 15, 2004 at 08:06:45AM +0200, Jarmo wrote:

(Adding mailing list back to Cc list because your mail server doesn't accept
my mails)

> > Let me know how well this is working.  I've tested this as well as possible
> > without having 6pack hardware myself and that's not too much ...  Anyway,
> > I need testers before I send this patch upstream with good conscious and
> > that means it at least has to reach stability comparable to what's in stock
> > 2.6.4.
> >
> > This patch is also available on ftp.linux-mips.net in /pub/ham/6pack/.
> >
> > 73 de DO1GRB op Ralf
> 
> Hi Ralf
> 
> FB that someone tries to modernize these things.

Exactly.  6pack.c and mkiss are derived from slip.c which being an uncommon
protocol these days is also suffering from bitrot.  Many of the past
updates for 6pack.c and mkiss were following the path set by slip.c ...

Admitedly, there are few good examples for how to write a line discipline
like slip.  PPP is reasonably well written but a way too complex protocol
to be a good example, n_tty.c is too simple to be useful and the Linux tty
code is hard to read.  So in short, there's a lack of good and simple
examples, maybe one reason of several why this code was suffering from
bitrot so badly ...

> Now,how I patch my 6pack.c...Normally I do it by command..
> 
> cat "file-patch.diff" | patch -p0
> 
> With this patch that does not work.

Well, you didn't say how it failed so I can only guess ...

Well, the command is right asssuming your working directory was the root
directory of the kernel source tree like in this example:

  cd /usr/src/linux-2.6.4
  patch -p0 < 2.6.3-6pack-6.diff

Just in case if the patch file got corrupted, ftp it from ftp.linux-mips.net
in /pub/ham/6pack/.

  Ralf


      parent reply	other threads:[~2004-03-15 13:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-12 11:10 Timers in 2.6.x kernels Jarmo
2004-03-12 19:09 ` Jeroen Vreeken
2004-03-13 14:19 ` Ralf Baechle DO1GRB
2004-03-13 14:59   ` Jarmo
2004-03-13 22:06     ` Ralf Baechle DO1GRB
2004-03-14  6:01       ` Jarmo
2004-03-15  0:51         ` Ralf Baechle DO1GRB
     [not found]           ` <200403150806.46071.oh1mrr@nic.fi>
2004-03-15 13:38             ` Ralf Baechle [this message]

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=20040315133825.GA3483@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-hams@vger.kernel.org \
    --cc=oh1mrr@nic.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