All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: neilb@cse.unsw.edu.au
Cc: ak@suse.de, linux-kernel@vger.kernel.org, aeb@cwi.nl
Subject: Re: sendmsg and IP_PKTINFO
Date: Thu, 20 Feb 2003 20:17:49 -0800 (PST)	[thread overview]
Message-ID: <20030220.201749.75380162.davem@redhat.com> (raw)
In-Reply-To: <15957.41515.937965.343498@notabene.cse.unsw.edu.au>

   From: Neil Brown <neilb@cse.unsw.edu.au>
   Date: Fri, 21 Feb 2003 14:51:07 +1100
   
   As far as I can tell, control message are currently defined for:
      IPv4,
      IPv6,
      SOL_HCI - some bluetooth thing
      SOL_SOCKET (which don't seem to be clearly documented in socket(7))
   
Also, control messages are used for AF_UNIX to pass file descriptors
around.

  reply	other threads:[~2003-02-21  4:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <15954.4693.893707.471216@notabene.cse.unsw.edu.au.suse.lists.linux.kernel>
     [not found] ` <200302181606.TAA03838@sex.inr.ac.ru.suse.lists.linux.kernel>
     [not found]   ` <15954.49970.860809.75554@notabene.cse.unsw.edu.au.suse.lists.linux.kernel>
     [not found]     ` <20030218.155651.108799644.davem@redhat.com.suse.lists.linux.kernel>
2003-02-19  8:17       ` sendmsg and IP_PKTINFO Andi Kleen
2003-02-19  8:06         ` David S. Miller
2003-02-21  3:51         ` Neil Brown
2003-02-21  4:17           ` David S. Miller [this message]
2003-02-18 19:57 Julian Anastasov
2003-02-18 23:39 ` Neil Brown
  -- strict thread matches above, loose matches on Subject: below --
2003-02-15  1:53 Neil Brown
2003-02-18  7:10 ` David S. Miller
2003-02-18 11:00   ` sendmsg and IP_PKTINFO Neil Brown
2003-02-18 16:06     ` kuznet
2003-02-18 23:35       ` Neil Brown
2003-02-18 23:56         ` David S. Miller
2003-02-19  3:52     ` David S. Miller
2003-02-19  4:13       ` Neil Brown
2003-02-19  4:03         ` David S. 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=20030220.201749.75380162.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=aeb@cwi.nl \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.