From: Pidoux <f6bvp@free.fr>
To: David Miller <davem@davemloft.net>
Cc: bpidoux@free.fr, ralf@linux-mips.org, netdev@vger.kernel.org,
linux-hams@vger.kernel.org
Subject: Re: [PATCH] [ROSE] improving AX25 routing frames
Date: Wed, 16 Jul 2008 19:29:50 +0200 [thread overview]
Message-ID: <487E300E.3020601@free.fr> (raw)
In-Reply-To: <20080714.231423.94246492.davem@davemloft.net>
David,
This is great news indeed.
I am not pulling net-next-2.6 GIT tree, but only net-2.6.
As I did not received any acknowledgement I thought you did not had time to review my patch.
Thanks a lot.
Bernard
David Miller a écrit :
> From: Bernard Pidoux <bpidoux@free.fr>
> Date: Sat, 12 Jul 2008 11:32:56 +0200
>
>> You probably did not notice the following patch I re-sent a while ago at
>> your request:
>>
>> 200806071944.07304.bpidoux () free ! fr
>>
>> Although it is not critical for Linux kernel and for general users, it
>> it of valuable interest for the digital hamradio community as it repairs
>> the rose network routing and gives us the connectivity we are lacking.
>
> It's been in my net-next-2.6 GIT tree for weeks, and I will merge it
> in during the 2.6.27 merge window.
> --
--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-07-16 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200804251659.47510.bpidoux@free.fr>
[not found] ` <20080426.230111.49125483.davem@davemloft.net>
[not found] ` <4836E223.8080003@upmc.fr>
[not found] ` <20080603.145827.170048802.davem@davemloft.net>
2008-07-12 9:32 ` [PATCH] [ROSE] improving AX25 routing frames Bernard Pidoux
2008-07-15 6:14 ` David Miller
2008-07-16 17:29 ` Pidoux [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=487E300E.3020601@free.fr \
--to=f6bvp@free.fr \
--cc=bpidoux@free.fr \
--cc=davem@davemloft.net \
--cc=linux-hams@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.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 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.