From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: nfbz 621 - 3 kernel patches
Date: Mon, 25 Jan 2010 13:09:34 +0100 [thread overview]
Message-ID: <4B5D89FE.2060809@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.01.1001251201260.31060@obet.zrqbmnf.qr>
Jan Engelhardt wrote:
> On Monday 2009-12-14 14:51, Patrick McHardy wrote:
>> Jan Engelhardt wrote:
>>> a few simple commits that turned up while processing NF bug 621.
>>> Thanks for taking care of them :)
>>>
>>> The following changes since commit 22763c5cf3690a681551162c15d34d935308c8d7:
>>> Linus Torvalds (1):
>>> Linux 2.6.32
>>>
>>> are available in the git repository at:
>>>
>>> git://dev.medozas.de/linux master
>> I'll apply those once the net-next tree opens up.
>
> Is it open already? :)
Yes, but I don't have those patches in my inbox anymore. Please
resend based on nf-next-2.6.git.
next prev parent reply other threads:[~2010-01-25 12:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-05 20:26 nfbz 621 - 3 kernel patches Jan Engelhardt
2009-12-05 20:26 ` [PATCH 1/3] netfilter: xt_recent: save 8 bytes per htable Jan Engelhardt
2010-01-04 15:26 ` Patrick McHardy
2009-12-05 20:26 ` [PATCH 2/3] netfilter: xtables: do not grab random bytes at __init Jan Engelhardt
2010-01-04 15:27 ` Patrick McHardy
2009-12-05 20:26 ` [PATCH 3/3] netfilter: xtables: obtain random bytes earlier, in checkentry Jan Engelhardt
2010-01-04 15:29 ` Patrick McHardy
2009-12-14 13:51 ` nfbz 621 - 3 kernel patches Patrick McHardy
2010-01-25 11:01 ` Jan Engelhardt
2010-01-25 12:09 ` Patrick McHardy [this message]
2010-01-25 23:05 ` Jan Engelhardt
2010-01-26 11:08 ` 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=4B5D89FE.2060809@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.