netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: ralf@linux-mips.org
Cc: netdev@vger.kernel.org
Subject: Re: [AX.25 1/2] Introduce struct ax25_sock.
Date: Sat, 22 Jul 2006 01:36:18 -0700 (PDT)	[thread overview]
Message-ID: <20060722.013618.71088903.davem@davemloft.net> (raw)
In-Reply-To: <20060721152946.GA16317@linux-mips.org>

From: Ralf Baechle <ralf@linux-mips.org>
Date: Fri, 21 Jul 2006 11:29:46 -0400

> Upto now AX.25 was using two separate structures for it's sockets.  One,
> ax25_cb described the entire actual AX.25 connection.  The other was
> the standard struct sock.
> 
> This patch combines both into struct ax25_sock which is more in line with
> current practice.  An AX.25 speciality was that a ax25_cb could exist
> without a struct sock referencing it.  Keep that alive for now by keeping
> the old struct sock *sk member of ax25_cb in struct ax25_sock.  This now
> just has become a struct-internal pointer.
> 
> Aside of wanrouter AX.25 has also been the last member of struct
> sock.sk_protinfo.  With net/wanrouter being considered hopeless code and
> an application-level solution being prefered these days this means we now
> can delete sk_protinfo.
> 
> Signed-off-by: Ralf Baechle <ralf@linux-mips.org>

This is very nice work Ralf, but I think it's 2.6.19 material.
:-)

  parent reply	other threads:[~2006-07-22  8:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-21 15:29 [AX.25 1/2] Introduce struct ax25_sock Ralf Baechle
2006-07-21 15:36 ` [AX.25 2/2] Fix reference counting by socket timers Ralf Baechle
2006-07-21 17:26 ` [AX.25 1/2] Introduce struct ax25_sock Arnaldo Carvalho de Melo
2006-07-22  8:36 ` David Miller [this message]
2006-07-22 12:13   ` Ralf Baechle
2006-07-23  0:05     ` David 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=20060722.013618.71088903.davem@davemloft.net \
    --to=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).