From: Ralf Baechle DL5RB <ralf@linux-mips.org>
To: "Mike McCarthy, W1NR" <lists@w1nr.net>
Cc: 'Douglas Cole' <doug.n7bfs@gmail.com>, linux-hams@vger.kernel.org
Subject: Re: AX25 patches and how it affects the end user
Date: Fri, 13 Jan 2006 21:09:25 +0000 [thread overview]
Message-ID: <20060113210925.GB3516@linux-mips.org> (raw)
In-Reply-To: <000d01c616fc$5624f4b0$3849a8c0@lan.w1nr.net>
On Wed, Jan 11, 2006 at 05:14:05PM -0500, Mike McCarthy, W1NR wrote:
> Hi Douglas,
> Your best bet is to run the latest "stable" release. Unstable's are for
> those with time and expertise to "hack".
> It all depends on when Debian updates it's kernel. The patches have gone
> into the latest "git" on Kernel.org. When Debian fetches the kernel from
> there is anyone's guess. In about another week, SuSE will release 10.1
> Beta1. I don't even know if it will get into that. You can always install
> Debian and get the kernel source from kernel.org and build it. I would at
> least wait until 2.6.15.1 (in kernel.org's numbering) instead of trying to
> patch things.
> If Debian is running the 2.6.14 kernel, then you are probably OK. The
> changes that broke it are not in that version. These "patches" that you see
> are due to recent changes for multiprocessor hardware, but other things got
> broken at the same time.
Not quite. The locking bugs in mkiss were introduced when adding SMACK
support. When a little later the locking code - really only relevant to
multiprocessor or preemptable kernels - was changed, the bugs started to
show up on uniprocessor kernels as well.
Shit happens - but better let's fix it.
Ralf
next prev parent reply other threads:[~2006-01-13 21:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 17:45 AX25 patches and how it affects the end user Douglas Cole
2006-01-11 22:14 ` Mike McCarthy, W1NR
2006-01-12 0:55 ` Douglas Cole
2006-01-13 21:09 ` Ralf Baechle DL5RB [this message]
2006-01-17 16:59 ` Bernard Pidoux
2006-01-18 1:08 ` Ralf Baechle DL5RB
2006-01-18 8:38 ` ROSE lockup fix Ralf Baechle DL5RB
2006-01-19 16:44 ` Bernard Pidoux
2006-02-09 16:25 ` Bernard Pidoux
2006-01-18 12:26 ` AX25 patches and how it affects the end user Chuck Hast
2006-01-18 21:52 ` Ralf Baechle DL5RB
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=20060113210925.GB3516@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=doug.n7bfs@gmail.com \
--cc=linux-hams@vger.kernel.org \
--cc=lists@w1nr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.