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 17:05:44 -0700 (PDT) [thread overview]
Message-ID: <20060722.170544.21927031.davem@davemloft.net> (raw)
In-Reply-To: <20060722121343.GA7579@linux-mips.org>
From: Ralf Baechle <ralf@linux-mips.org>
Date: Sat, 22 Jul 2006 08:13:43 -0400
> While this patch itself is more of a cleanup it's a prerequisite for
> being able the use the sk_*_timer functions to fix the reference counts
> in AX.25 timers ...
When you have those timer refcount fixes as part of your patch set, I
can then justify putting the change into 2.6.18. Feel free to
resubmit once you have it all ready.
prev parent reply other threads:[~2006-07-23 0:05 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
2006-07-22 12:13 ` Ralf Baechle
2006-07-23 0:05 ` David Miller [this message]
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.170544.21927031.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).