From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: ip_tables: foreachs and reentrancy
Date: Thu, 25 Feb 2010 12:09:39 +0100 [thread overview]
Message-ID: <4B865A73.8020804@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.01.1002251205280.4362@obet.zrqbmnf.qr>
Jan Engelhardt wrote:
> On Thursday 2010-02-25 11:24, Patrick McHardy wrote:
>>> My intention was to have the entire set merged by 2.6.32, only
>>> delayed by my own tinkering around with the get_cycle measurement of
>>> the data collapse. But it was ready on-time for the 2.6.34 window!
>>> What went wrong? Do we need to begin the merge-into-kabernext window
>>> much earlier?
>> Yes, you should begin submitting patches when net-next opens,
>> usually at -rc1.
>
> Thanks for clearing this point of doubt up - I was under the
> impression that submissions were only accepted when kaber-next
> opens.
It opens when submissions show up :)
next prev parent reply other threads:[~2010-02-25 11:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 10:20 ip_tables: foreachs and reentrancy Jan Engelhardt
2010-02-12 10:20 ` [PATCH 1/6] netfilter: xtables: replace XT_ENTRY_ITERATE macro Jan Engelhardt
2010-02-13 10:29 ` Amos Jeffries
2010-02-13 10:39 ` Jan Engelhardt
2010-02-13 10:42 ` Amos Jeffries
2010-02-12 10:20 ` [PATCH 2/6] netfilter: xtables: optimize call flow around xt_entry_foreach Jan Engelhardt
2010-02-12 10:20 ` [PATCH 3/6] netfilter: xtables: replace XT_MATCH_ITERATE macro Jan Engelhardt
2010-02-12 10:20 ` [PATCH 4/6] netfilter: xtables: optimize call flow around xt_ematch_foreach Jan Engelhardt
2010-02-12 10:20 ` [PATCH 5/6] netfilter: xtables: reduce arguments to translate_table Jan Engelhardt
2010-02-12 10:20 ` [PATCH 6/6] netfilter: xtables2: make ip_tables reentrant Jan Engelhardt
2010-02-24 17:40 ` ip_tables: foreachs and reentrancy Patrick McHardy
2010-02-24 19:33 ` Jan Engelhardt
2010-02-25 10:24 ` Patrick McHardy
2010-02-25 11:07 ` Jan Engelhardt
2010-02-25 11:09 ` Patrick McHardy [this message]
2010-02-26 16:54 ` Patrick McHardy
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=4B865A73.8020804@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--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).