From: Bernard Pidoux <pidoux@ccr.jussieu.fr>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, linux-hams@vger.kernel.org
Subject: Re: [PATCH 3/3] Eleminate HZ from ROSE kernel interfaces
Date: Sun, 30 Apr 2006 11:35:54 +0200 [thread overview]
Message-ID: <445484FA.6050008@ccr.jussieu.fr> (raw)
In-Reply-To: <20060429141924.GA2941@linux-mips.org>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
Ralf Baechle wrote :
> Index: linux-net.git/net/rose/af_rose.c
> ===================================================================
> --- linux-net.git.orig/net/rose/af_rose.c 2006-04-29 01:54:21.000000000 +0100
> +++ linux-net.git/net/rose/af_rose.c 2006-04-29 11:37:34.000000000 +0100
While patching af_rose.c, would you consider the following patch
ROSE/FPAC users have introduced a year ago with good success.
73 de Bernard, f6bvp
http://f6bvp.org
http://rose.fpac.free.fr/MINI-HOWTO/
http://rose.fpac.free.fr/MINI-HOWTO-FR/
[-- Attachment #2: af_rose.diff --]
[-- Type: text/x-patch, Size: 716 bytes --]
--- linux/net/rose/af_rose.c.orig 2006-04-30 11:30:48.000000000 +0200
+++ linux/net/rose/af_rose.c 2006-04-30 11:27:35.000000000 +0200
@@ -753,6 +753,7 @@
rose_insert_socket(sk); /* Finish the bind */
}
+rose_try_next_neigh:
rose->dest_addr = addr->srose_addr;
rose->dest_call = addr->srose_call;
rose->rand = ((long)rose & 0xFFFF) + rose->lci;
@@ -810,6 +811,11 @@
}
if (sk->sk_state != TCP_ESTABLISHED) {
+ /* Try next neighbour */
+ rose->neighbour = rose_get_neigh(&addr->srose_addr, &cause, &diagnostic);
+ if (rose->neighbour)
+ goto rose_try_next_neigh;
+ /* No more neighbour */
sock->state = SS_UNCONNECTED;
return sock_error(sk); /* Always set at this point */
}
next prev parent reply other threads:[~2006-04-30 9:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-29 14:19 [PATCH 3/3] Eleminate HZ from ROSE kernel interfaces Ralf Baechle
2006-04-30 9:35 ` Bernard Pidoux [this message]
2006-05-04 6:28 ` David S. 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=445484FA.6050008@ccr.jussieu.fr \
--to=pidoux@ccr.jussieu.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 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).