From: Tommy Christensen <tommy.christensen@tpack.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev@oss.sgi.com, chamas@h4.dion.ne.jp
Subject: Re: [PATCH] netlink: defer socket destruction a bit
Date: Fri, 20 May 2005 01:15:37 +0200 [thread overview]
Message-ID: <428D1E19.9030204@tpack.net> (raw)
In-Reply-To: <20050519213839.GC24024@gondor.apana.org.au>
Herbert Xu wrote:
> On Thu, May 19, 2005 at 01:08:59PM -0700, David S. Miller wrote:
>
>>Ok, I think I got all the patches straight. All of Tommy's
>>patches combined together look like this diff in my tree.
>>Please double check it.
>
> Yes this is the one.
Yup. This combination fixes both problems.
Thanks,
Tommy
next prev parent reply other threads:[~2005-05-19 23:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 22:19 [PATCH] netlink: defer socket destruction a bit Tommy Christensen
2005-05-11 22:24 ` Herbert Xu
2005-05-11 22:35 ` Tommy Christensen
2005-05-11 23:03 ` Herbert Xu
2005-05-12 9:57 ` Tommy Christensen
2005-05-12 10:36 ` Herbert Xu
2005-05-19 20:08 ` David S. Miller
2005-05-19 21:38 ` Herbert Xu
2005-05-19 23:15 ` Tommy Christensen [this message]
2005-05-19 23:16 ` 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=428D1E19.9030204@tpack.net \
--to=tommy.christensen@tpack.net \
--cc=chamas@h4.dion.ne.jp \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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).