From: Bernard Pidoux F6BVP <f6bvp@free.fr>
To: David Miller <davem@davemloft.net>
Cc: Linux Netdev List <netdev@vger.kernel.org>
Subject: [ROSE] 2.6.29 rose patch missing in 2.6.30
Date: Sun, 21 Jun 2009 12:42:58 +0200 [thread overview]
Message-ID: <4A3E0EB2.7020106@free.fr> (raw)
Hi David,
Problems with ROSE protocol came back with 2.6.30 kernel.
I discovered the reason.
Rose patch I submitted in November was applied in kernels until 2.6.29.4.
However this patch is not present in 2.6.30.
Is there any reason ?
Here are the reference to my patch and your acceptance message :
List: linux-netdev
Subject: [PATCH] [ROSE] zero length frame filtering in af_rose.c
From: Bernard Pidoux <bernard.pidoux () upmc ! fr>
Date: 2008-11-24 21:49:40
Message-ID: 492B2174.1030503 () upmc ! fr
-----------
List: linux-hams
Subject: Re: [PATCH] [ROSE] zero length frame filtering in af_rose.c
From: David Miller <davem () davemloft ! net>
Date: 2008-11-25 8:57:50
Message-ID: 20081125.005750.41495501.davem () davemloft ! net
[Download message RAW]
Patch applied, thank you.
--
Regards,
Bernard Pidoux
next reply other threads:[~2009-06-21 10:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-21 10:42 Bernard Pidoux F6BVP [this message]
2009-06-21 10:56 ` [ROSE] 2.6.29 rose patch missing in 2.6.30 David Miller
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=4A3E0EB2.7020106@free.fr \
--to=f6bvp@free.fr \
--cc=davem@davemloft.net \
--cc=netdev@vger.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).