From: David Miller <davem@davemloft.net>
To: David.Laight@ACULAB.COM
Cc: eric.dumazet@gmail.com, netdev@vger.kernel.org
Subject: Re: sock_getsockopt() not exported
Date: Fri, 19 Oct 2012 13:12:56 -0400 (EDT) [thread overview]
Message-ID: <20121019.131256.2026785630531870853.davem@davemloft.net> (raw)
In-Reply-To: <AE90C24D6B3A694183C094C60CF0A2F6026B7056@saturn3.aculab.com>
From: "David Laight" <David.Laight@ACULAB.COM>
Date: Fri, 19 Oct 2012 10:26:52 +0100
> The Linux interface is all done with wrapper functions
> that get compiled on the target system so we can ship
> a big binary 'blob'.
Your maintainence problem, not our's.
next prev parent reply other threads:[~2012-10-19 17:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 9:11 sock_getsockopt() not exported David Laight
2012-10-18 9:30 ` Eric Dumazet
2012-10-18 12:03 ` David Laight
2012-10-18 12:27 ` Eric Dumazet
2012-10-19 9:26 ` David Laight
2012-10-19 17:12 ` David Miller [this message]
2012-10-18 19:04 ` 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=20121019.131256.2026785630531870853.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=David.Laight@ACULAB.COM \
--cc=eric.dumazet@gmail.com \
--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).