From: Ralf Baechle <ralf@linux-mips.org>
To: Pidoux <f6bvp@free.fr>, Jeff Garzik <jeff@garzik.org>, stable@kernel.org
Cc: David Robb <ender@paradise.gen.nz>,
linux-hams@vger.kernel.org, David Miller <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: baycom_ser_fdx - fixed under 2.6
Date: Tue, 22 Jul 2008 13:08:46 +0100 [thread overview]
Message-ID: <20080722120846.GA26093@linux-mips.org> (raw)
In-Reply-To: <4885A8F6.7090109@free.fr>
On Tue, Jul 22, 2008 at 11:31:34AM +0200, Pidoux wrote:
> This is a trivial but very important bug fix. Thanks David.
> It was probably not submitted to the right destination and thus never applied.
>
> This bug may have discouraged more than one radioamateur wishing to experiment baycom style modems under Linux.
> Fortunately you have done a very good historical search.
>
> I rebuilt the patch against 2.6.26 kernel (the only source I have here on my laptop at my remote location during vacation).
>
> I Cc: to David Miller and Ralf Baechle DL5RB maintainers of Linux net devices drivers and Linux AX25 drivers, respectively.
Correct, the CRC should go at the end of the frame, not corrupt the first
header bytes. So this one should also go into -stable.
Acked-by: Ralf Baechle <ralf@linux-mips.org>
Ralf
next prev parent reply other threads:[~2008-07-22 12:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.1.10.0807191042050.21295@tombstone.paradise.gen.nz>
2008-07-22 9:31 ` baycom_ser_fdx - fixed under 2.6 Pidoux
2008-07-22 12:08 ` Ralf Baechle [this message]
2008-07-28 3:44 ` Peter Mallett
2008-07-28 10:32 ` Matti Aarnio
2008-07-29 0:01 ` Peter Mallett
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=20080722120846.GA26093@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=davem@davemloft.net \
--cc=ender@paradise.gen.nz \
--cc=f6bvp@free.fr \
--cc=jeff@garzik.org \
--cc=linux-hams@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@kernel.org \
/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).