From: "David S. Miller" <davem@davemloft.net>
To: bunk@stusta.de
Cc: akpm@osdl.org, netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] net/socket.c: unexport move_addr_to_kernel
Date: Thu, 02 Jun 2005 13:14:28 -0700 (PDT) [thread overview]
Message-ID: <20050602.131428.28787855.davem@davemloft.net> (raw)
In-Reply-To: <20050530205647.GW10441@stusta.de>
From: Adrian Bunk <bunk@stusta.de>
Date: Mon, 30 May 2005 22:56:47 +0200
> I didn't find any modular usage in the kernel.
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
Yes, but as a part of the socket kernel API, I could
definitely see some out-of-tree code legitimately
using this interface. Let's keep it around for now.
next prev parent reply other threads:[~2005-06-02 20:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-30 20:56 [2.6 patch] net/socket.c: unexport move_addr_to_kernel Adrian Bunk
2005-06-02 20:14 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-06 22:27 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=20050602.131428.28787855.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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).