From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
Jorrit Kronjee <j.kronjee@infopact.nl>,
netfilter-devel@vger.kernel.org, netdev <netdev@vger.kernel.org>
Subject: Re: debugging kernel during packet drops
Date: Tue, 30 Mar 2010 16:12:59 +0200 [thread overview]
Message-ID: <4BB206EB.1000808@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.01.1003301405490.10802@obet.zrqbmnf.qr>
Jan Engelhardt wrote:
> On Thursday 2010-03-25 11:35, Patrick McHardy wrote:
>
>> This clashes with some recent cleanups in nf-next-2.6.git. I'm
>> also expecting a patch from Jan to remove the old v0 revision
>> very soon (probably today). Please rediff once I've pushed that out.
>
> One 12-series request has been sitting there for a while. Was there
> something not in order with it?
No, I'm currently a bit backlogged due to getting sick. I'm running
your series for testing though, I'll probably push it out tommorrow.
prev parent reply other threads:[~2010-03-30 14:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4BA74950.6000305@infopact.nl>
[not found] ` <4BA7A5D8.5080101@trash.net>
[not found] ` <4BA8DAC5.6050002@infopact.nl>
[not found] ` <1269364893.2983.296.camel@edumazet-laptop>
[not found] ` <4BAA2DC5.7000409@infopact.nl>
[not found] ` <1269447674.3213.64.camel@edumazet-laptop>
2010-03-25 9:32 ` debugging kernel during packet drops Eric Dumazet
2010-03-25 10:35 ` Patrick McHardy
2010-03-25 11:02 ` Eric Dumazet
2010-03-31 12:23 ` [PATCH nf-next-2.6] xt_hashlimit: RCU conversion Eric Dumazet
2010-04-01 11:03 ` Patrick McHardy
2010-04-01 12:10 ` Eric Dumazet
2010-04-01 12:36 ` Patrick McHardy
2010-03-25 12:42 ` debugging kernel during packet drops Jan Engelhardt
2010-03-30 12:06 ` Jan Engelhardt
2010-03-30 14:12 ` Patrick McHardy [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=4BB206EB.1000808@trash.net \
--to=kaber@trash.net \
--cc=eric.dumazet@gmail.com \
--cc=j.kronjee@infopact.nl \
--cc=jengelh@medozas.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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).