From: "David S. Miller" <davem@redhat.com>
To: bcrl@redhat.com
Cc: netdev@oss.sgi.com
Subject: Re: [patch] abstract out socket lock.users access
Date: Mon, 07 Oct 2002 15:53:32 -0700 (PDT) [thread overview]
Message-ID: <20021007.155332.32735975.davem@redhat.com> (raw)
In-Reply-To: <20021007185051.A25468@redhat.com>
From: Benjamin LaHaise <bcrl@redhat.com>
Date: Mon, 7 Oct 2002 18:50:51 -0400
Anyways, this version should be cleaned up, unless my eyes have glossed over
and missed something in reading through the patch.
Looks good, the sock_owned_by_user() is a needed good cleanup in
any event.
After some sleep I'll think some more about the async machinery
and probably just apply this unless someone else finds something
terribly wrong.
prev parent reply other threads:[~2002-10-07 22:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 21:55 [patch] abstract out socket lock.users access Benjamin LaHaise
2002-10-07 22:14 ` David S. Miller
2002-10-07 22:50 ` Benjamin LaHaise
2002-10-07 22:53 ` David S. Miller [this message]
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=20021007.155332.32735975.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).