From: Jesper Dangaard Brouer <brouer@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: khlebnikov@openvz.org, netdev@vger.kernel.org
Subject: Re: [PATCH] net: frag, fix race conditions in LRU list maintenance
Date: Wed, 8 May 2013 17:32:27 +0200 [thread overview]
Message-ID: <20130508173227.0f773360@redhat.com> (raw)
In-Reply-To: <20130506.110800.1388239604905052651.davem@davemloft.net>
On Mon, 06 May 2013 11:08:00 -0400 (EDT) David Miller <davem@davemloft.net> wrote:
> I sorted out the conflicts but someone needs to double-check
> my work.
Looks good to me.
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Sr. Network Kernel Developer at Red Hat
Author of http://www.iptv-analyzer.org
LinkedIn: http://www.linkedin.com/in/brouer
prev parent reply other threads:[~2013-05-08 15:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-05 14:56 [PATCH] net: frag, fix race conditions in LRU list maintenance Konstantin Khlebnikov
2013-05-05 17:36 ` David Miller
2013-05-05 18:30 ` Florian Westphal
2013-05-06 7:33 ` Jesper Dangaard Brouer
2013-05-06 15:08 ` David Miller
2013-05-07 5:22 ` Konstantin Khlebnikov
2013-05-07 9:13 ` David Miller
2013-05-08 15:32 ` Jesper Dangaard Brouer [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=20130508173227.0f773360@redhat.com \
--to=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=khlebnikov@openvz.org \
--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).