From: Bernard Pidoux <pidoux@ccr.jussieu.fr>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: Ralf Baechle DL5RB <ralf@linux-mips.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
David Miller <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [PATCH 2/4] [ROSE] rose_get_route() template
Date: Tue, 15 Jan 2008 15:42:35 +0100 [thread overview]
Message-ID: <478CC65B.9000505@ccr.jussieu.fr> (raw)
In-Reply-To: <47893127.2080606@ccr.jussieu.fr>
Hi,
I wrote a "simplified" get_route() function.
It is declared as static following judicious Eric's remark.
Then, the following patch of include/net/rose.h is no more
necessary.
A new commit for rose_get_route() will be presented in next
message.
Thank you Eric for pushing me to reexamine my code.
Regards,
Bernard P.
Bernard Pidoux wrote:
>
>
> Eric Dumazet wrote:
>> Bernard Pidoux a écrit :
>>> From 46bccce1e660a39bcc8f8cf87d4c17de33f4ba48 Mon Sep 17 00:00:00 2001
>>> From: Bernard Pidoux <f6bvp@amsat.org>
>>> Date: Thu, 10 Jan 2008 23:01:46 +0100
>>> Subject: [PATCH 2/4] [ROSE] template declaration for rose_get_route()
>>>
>>> Signed-off-by: Bernard Pidoux <f6bvp@amsat.org>
>>> ---
>>> include/net/rose.h | 1 +
>>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/include/net/rose.h b/include/net/rose.h
>>> index e5bb084..d3ab453 100644
>>> --- a/include/net/rose.h
>>> +++ b/include/net/rose.h
>>> @@ -202,6 +202,7 @@ extern struct net_device *rose_dev_first(void);
>>> extern struct net_device *rose_dev_get(rose_address *);
>>> extern struct rose_route *rose_route_free_lci(unsigned int, struct
>>> rose_neigh *);
>>> extern struct rose_neigh *rose_get_neigh(rose_address *, unsigned
>>> char *, unsigned char *);
>>> +extern struct rose_neigh *rose_get_route(rose_address *, unsigned
>>> char *, unsigned char *);
>>> extern int rose_rt_ioctl(unsigned int, void __user *);
>>> extern void rose_link_failed(ax25_cb *, int);
>>> extern int rose_route_frame(struct sk_buff *, ax25_cb *);
>>> --
>>
>> Strange... if rose_get_route() is used only in net/rose/rose_route.c,
>> why dont you define it static, and not extern in include/net/rose.h ?
>>
>>
>>
>
> I agree. You are perfectly right.
> There is no need to declare rose_get_route() external.
> I stupidly copied rose_get_neigh()definition from which I derived
> rose_get_route();
>
> Also I am not sure that setting cause and diagnostic is necessary, as
> they are not used by the calling function.
>
> By the way. I made a typo in [PATCH 4/4].
>
> Instead of "Initial connection to rose neighbour nodes was unusually,
> t0 timer was blocked and application program could not
> use socket."
>
> One should read
> "Initial connection to rose neighbour nodes was unusually,
> long, t0 timer was blocked and application program could not
> use socket."
>
> Bernard P.
>
>
>
next prev parent reply other threads:[~2008-01-15 14:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 22:23 [PATCH] [ROSE] finding a connected ROSE neighbor node Bernard Pidoux
2008-01-12 20:15 ` Bernard Pidoux
2008-01-12 20:17 ` [PATCH 2/4] [ROSE] rose_get_route() template Bernard Pidoux
2008-01-12 20:33 ` Eric Dumazet
2008-01-12 21:29 ` Bernard Pidoux
2008-01-15 14:42 ` Bernard Pidoux [this message]
2008-01-12 20:20 ` [PATCH 3/4] [ROSE] return with lock held Bernard Pidoux
2008-01-12 20:23 ` [PATCH 4/4] [ROSE] ENETUNREACH held rose_connect() Bernard Pidoux
2008-01-15 15:00 ` [PATCH 1/4] [ROSE] simplified rose_get_route() Bernard Pidoux
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=478CC65B.9000505@ccr.jussieu.fr \
--to=pidoux@ccr.jussieu.fr \
--cc=adobriyan@gmail.com \
--cc=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--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).