From: "David S. Miller" <davem@davemloft.net>
To: bunk@stusta.de
Cc: netdev@vger.kernel.org
Subject: Re: [2.6 patch] net/ipv4/: possible cleanups
Date: Wed, 12 Apr 2006 13:54:02 -0700 (PDT) [thread overview]
Message-ID: <20060412.135402.37104713.davem@davemloft.net> (raw)
In-Reply-To: <20060412202225.GD6517@stusta.de>
From: Adrian Bunk <bunk@stusta.de>
Date: Wed, 12 Apr 2006 22:22:25 +0200
> Done.
I was eagerly awaiting this after seeing the wan drivers disappear.
Thanks Bunk-bot. :-)
next prev parent reply other threads:[~2006-04-12 20:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060404163701.GS6529@stusta.de>
[not found] ` <20060405.222543.118196555.davem@davemloft.net>
[not found] ` <20060406084909.GL8673@stusta.de>
[not found] ` <20060406.133857.40478787.davem@davemloft.net>
2006-04-12 20:22 ` [2.6 patch] net/ipv4/: possible cleanups Adrian Bunk
2006-04-12 20:54 ` David S. Miller [this message]
2005-07-23 22:05 Adrian Bunk
2005-07-25 19:42 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2005-05-30 20:56 [RFC: 2.6 " Adrian Bunk
2005-06-02 20:13 ` David S. Miller
2005-06-26 16:05 ` [2.6 " Adrian Bunk
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=20060412.135402.37104713.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bunk@stusta.de \
--cc=netdev@vger.kernel.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).