netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: ak@suse.de
Cc: olh@suse.de, marcelo@conectiva.com.br, netdev@oss.sgi.com
Subject: Re: comment about struct tcp_tw_bucket in struct sock
Date: Wed, 14 May 2003 13:02:32 -0700 (PDT)	[thread overview]
Message-ID: <20030514.130232.88490119.davem@redhat.com> (raw)
In-Reply-To: <20030514195731.GC31303@Wotan.suse.de>

   From: Andi Kleen <ak@suse.de>
   Date: Wed, 14 May 2003 21:57:31 +0200

   When they cut'n'paste structures they're completely on their own ...
   
Depends upon who's willing to support them.

   I hope you will never let stop such an omnious third party module
   you from doing any bug fix or optimization.
   
Aha, you're right and _I_ don't need to worry about this.  I'm merely
saying some vendor's _might_. :-)

But see, since it only matters in the main kernel, every attempt to
change the layout of struct sock will go through me before it hits the
vanilla tree, so as a result I'll catch such problems and we thus have
no problems :-)

You can't have it both ways Andi, either we care about arbitrary third
parties do or we don't.

  reply	other threads:[~2003-05-14 20:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-13 21:05 comment about struct tcp_tw_bucket in struct sock Olaf Hering
2003-05-13 23:31 ` David S. Miller
2003-05-14  2:44   ` Arnaldo Carvalho de Melo
2003-05-14  8:00   ` Olaf Hering
2003-05-14 19:17     ` David S. Miller
2003-05-14 19:23       ` Andi Kleen
2003-05-14 19:34         ` David S. Miller
2003-05-14 19:57           ` Andi Kleen
2003-05-14 20:02             ` David S. Miller [this message]
2003-05-14  8:32   ` Andi Kleen
2003-05-14 19:18     ` David S. Miller
2003-05-14 19:21       ` Andi Kleen
2003-05-22  0:52         ` Arnaldo Carvalho de Melo
2003-05-22  8:02           ` Andi Kleen

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=20030514.130232.88490119.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=ak@suse.de \
    --cc=marcelo@conectiva.com.br \
    --cc=netdev@oss.sgi.com \
    --cc=olh@suse.de \
    /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).