All of lore.kernel.org
 help / color / mirror / Atom feed
* [RFC] s/TCP_ESTABLISHED/PROTO_ESTABLISHED/g
@ 2002-01-10 16:16 Arnaldo Carvalho de Melo
  2002-01-10 16:21 ` David S. Miller
  0 siblings, 1 reply; 5+ messages in thread
From: Arnaldo Carvalho de Melo @ 2002-01-10 16:16 UTC (permalink / raw)
  To: davem; +Cc: Linux Kernel Mailing List

Dave,

	Part of the sock cleanup made me remove the #include <linux/tcp.h> from
include/linux/ip.h and from include/net/sock.h, i.e., it is not needed in
those headers, but then I had to go to udp.c, ipx.c, decnet, etc, and add a
#include <linux/tcp.h> because it needs TCP_ESTABLISHED, TCP_CLOSE, etc,
this is a pet peeve to me, as a janitor :-) Can I change this to
PROTO_ESTABLISHED, PROTO_CLOSE, etc, and have it on a different header, say
include/net/protocol.h?  Its strange to have IPX, DecNET, etc having to
include net/tcp.h (that in turn includes ip.h, etc).

	If this is ok I can bundle it in the sock cleanup or send it
separately, your call.

- Arnaldo

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [RFC] s/TCP_ESTABLISHED/PROTO_ESTABLISHED/g
  2002-01-10 16:16 [RFC] s/TCP_ESTABLISHED/PROTO_ESTABLISHED/g Arnaldo Carvalho de Melo
@ 2002-01-10 16:21 ` David S. Miller
  2002-01-10 17:06   ` Arnaldo Carvalho de Melo
  0 siblings, 1 reply; 5+ messages in thread
From: David S. Miller @ 2002-01-10 16:21 UTC (permalink / raw)
  To: acme; +Cc: linux-kernel

   From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
   Date: Thu, 10 Jan 2002 14:16:29 -0200

   	Part of the sock cleanup made me remove the #include <linux/tcp.h> from
   include/linux/ip.h and from include/net/sock.h, i.e., it is not needed in
   those headers, but then I had to go to udp.c, ipx.c, decnet, etc, and add a
   #include <linux/tcp.h> because it needs TCP_ESTABLISHED, TCP_CLOSE, etc,
   this is a pet peeve to me, as a janitor :-) Can I change this to
   PROTO_ESTABLISHED, PROTO_CLOSE, etc, and have it on a different header, say
   include/net/protocol.h?  Its strange to have IPX, DecNET, etc having to
   include net/tcp.h (that in turn includes ip.h, etc).
   
   	If this is ok I can bundle it in the sock cleanup or send it
   separately, your call.

These other protocols are just borrowing state machine states from
TCP.  I really see no reason to rename them, because then if you did
the TCP usage wouldn't make look right anymore. :-)

I don't mind moving the header include from sock.h to the protocols
though.

Franks a lot,
David S. Miller
davem@redhat.com

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [RFC] s/TCP_ESTABLISHED/PROTO_ESTABLISHED/g
  2002-01-10 16:21 ` David S. Miller
@ 2002-01-10 17:06   ` Arnaldo Carvalho de Melo
  2002-01-10 17:07     ` David S. Miller
  0 siblings, 1 reply; 5+ messages in thread
From: Arnaldo Carvalho de Melo @ 2002-01-10 17:06 UTC (permalink / raw)
  To: David S. Miller; +Cc: linux-kernel

Em Thu, Jan 10, 2002 at 08:21:41AM -0800, David S. Miller escreveu:
>    From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
>    Date: Thu, 10 Jan 2002 14:16:29 -0200
> 
>    	Part of the sock cleanup made me remove the #include <linux/tcp.h> from
>    include/linux/ip.h and from include/net/sock.h, i.e., it is not needed in
>    those headers, but then I had to go to udp.c, ipx.c, decnet, etc, and add a
>    #include <linux/tcp.h> because it needs TCP_ESTABLISHED, TCP_CLOSE, etc,
>    this is a pet peeve to me, as a janitor :-) Can I change this to
>    PROTO_ESTABLISHED, PROTO_CLOSE, etc, and have it on a different header, say
>    include/net/protocol.h?  Its strange to have IPX, DecNET, etc having to
>    include net/tcp.h (that in turn includes ip.h, etc).
>    
>    	If this is ok I can bundle it in the sock cleanup or send it
>    separately, your call.
> 
> These other protocols are just borrowing state machine states from
> TCP.  I really see no reason to rename them, because then if you did
> the TCP usage wouldn't make look right anymore. :-)
> 
> I don't mind moving the header include from sock.h to the protocols
> though.

just to make sure I understood: "to the protocols" means creating
IPX_ESTABLISHED, etc, or does it mean having the protocols include tcp.h?

- Arnaldo

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [RFC] s/TCP_ESTABLISHED/PROTO_ESTABLISHED/g
  2002-01-10 17:06   ` Arnaldo Carvalho de Melo
@ 2002-01-10 17:07     ` David S. Miller
  2002-01-10 17:13       ` Arnaldo Carvalho de Melo
  0 siblings, 1 reply; 5+ messages in thread
From: David S. Miller @ 2002-01-10 17:07 UTC (permalink / raw)
  To: acme; +Cc: linux-kernel

   From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
   Date: Thu, 10 Jan 2002 15:06:26 -0200
   
   just to make sure I understood: "to the protocols" means creating
   IPX_ESTABLISHED, etc, or does it mean having the protocols include tcp.h?

Include tcp.h

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [RFC] s/TCP_ESTABLISHED/PROTO_ESTABLISHED/g
  2002-01-10 17:07     ` David S. Miller
@ 2002-01-10 17:13       ` Arnaldo Carvalho de Melo
  0 siblings, 0 replies; 5+ messages in thread
From: Arnaldo Carvalho de Melo @ 2002-01-10 17:13 UTC (permalink / raw)
  To: David S. Miller; +Cc: linux-kernel

Em Thu, Jan 10, 2002 at 09:07:24AM -0800, David S. Miller escreveu:
>    From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
>    Date: Thu, 10 Jan 2002 15:06:26 -0200
>    
>    just to make sure I understood: "to the protocols" means creating
>    IPX_ESTABLISHED, etc, or does it mean having the protocols include tcp.h?
> 
> Include tcp.h

Ok, thats what is being done, works, but I still think its ugly, I'm a
nitpicker, you know 8-)

- Arnaldo

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2002-01-10 17:14 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-01-10 16:16 [RFC] s/TCP_ESTABLISHED/PROTO_ESTABLISHED/g Arnaldo Carvalho de Melo
2002-01-10 16:21 ` David S. Miller
2002-01-10 17:06   ` Arnaldo Carvalho de Melo
2002-01-10 17:07     ` David S. Miller
2002-01-10 17:13       ` Arnaldo Carvalho de Melo

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.