From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Netfilter Developer Mailing List <netfilter-devel@vger.kernel.org>
Subject: Re: nf-next: checks and misc
Date: Thu, 18 Mar 2010 14:51:43 +0100 [thread overview]
Message-ID: <4BA22FEF.4050208@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.01.1003181422230.17133@obet.zrqbmnf.qr>
Jan Engelhardt wrote:
> Hi,
>
>
> these are the issue-free parts of the previous submission (thus
> no repost of the commits themselves). Please merge.
>
>
> The following changes since commit e8a96f69383f3d88cdc06d8ccd450f70c48628a3:
> Patrick McHardy (1):
> Merge branch 'master' of ../nf-2.6
>
> are available in the git repository at:
>
> git://dev.medozas.de/linux master
>
> Jan Engelhardt (4):
> netfilter: xtables: do without explicit XT_ALIGN
> netfilter: xtables: clean up xt_mac match routine
> netfilter: xtables: limit xt_mac to ethernet devices
> netfilter: xtables: resort osf kconfig text
Pulled, thanks Jan.
prev parent reply other threads:[~2010-03-18 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 13:24 nf-next: checks and misc Jan Engelhardt
2010-03-18 13:51 ` 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=4BA22FEF.4050208@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).