From: "David S. Miller" <davem@redhat.com>
To: bcrl@redhat.com
Cc: netdev@oss.sgi.com
Subject: Re: [patch] add iocb to network protocols
Date: Thu, 10 Oct 2002 16:36:46 -0700 (PDT) [thread overview]
Message-ID: <20021010.163646.35014672.davem@redhat.com> (raw)
In-Reply-To: <20021010194025.B13432@redhat.com>
From: Benjamin LaHaise <bcrl@redhat.com>
Date: Thu, 10 Oct 2002 19:40:25 -0400
On Thu, Oct 10, 2002 at 04:22:40PM -0700, David S. Miller wrote:
>
> +#include <net/scm.h> /* for sock_iocb */
>
> What is this?
The private area of an iocb for network operations contains a struct
scm_cookie.
I know this. But the comment is wrong, when you say "for FOO"
next to an include that means "I'm including this to get the
definition of FOO".
Just delete the comment entirely, it really isn't needed.
Otherwise looks ok at first glance.
next prev parent reply other threads:[~2002-10-10 23:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 22:35 [patch] add iocb to network protocols Benjamin LaHaise
2002-10-10 23:22 ` David S. Miller
2002-10-10 23:40 ` Benjamin LaHaise
2002-10-10 23:36 ` David S. Miller [this message]
2002-10-11 20:15 ` kuznet
2002-10-11 20:24 ` Benjamin LaHaise
2002-10-11 9:31 ` Steven Whitehouse
2002-10-11 10:27 ` Benjamin LaHaise
2002-10-12 1:21 ` 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=20021010.163646.35014672.davem@redhat.com \
--to=davem@redhat.com \
--cc=bcrl@redhat.com \
--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).