From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: nf-next: struct optimization, print changes
Date: Fri, 19 Mar 2010 15:47:36 +0100 [thread overview]
Message-ID: <4BA38E88.4080203@trash.net> (raw)
In-Reply-To: <1268921390-30296-1-git-send-email-jengelh@medozas.de>
Jan Engelhardt wrote:
> Hi,
>
> here is a small mixed bag. struct optimization, using the established
> pr_ print functions. Please review.
>
>
These all look good to me. Can I assume you also want me to pull them in?
next prev parent reply other threads:[~2010-03-19 14:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 14:09 nf-next: struct optimization, print changes Jan Engelhardt
2010-03-18 14:09 ` [PATCH 1/7] netfilter: xtables: make use of caller family rather than match family Jan Engelhardt
2010-03-18 14:09 ` [PATCH 2/7] netfilter: update documentation fields of x_tables.h Jan Engelhardt
2010-03-18 14:09 ` [PATCH 3/7] netfilter: xtables: remove almost-unused xt_match_param.data member Jan Engelhardt
2010-03-18 14:09 ` [PATCH 4/7] netfilter: xtables: reduce holes in struct xt_target Jan Engelhardt
2010-03-18 14:09 ` [PATCH 5/7] netfilter: xtables: do not print any messages on ENOMEM Jan Engelhardt
2010-03-18 14:09 ` [PATCH 6/7] netfilter: xtables: replace custom duprintf with pr_debug Jan Engelhardt
2010-03-18 14:09 ` [PATCH 7/7] netfilter: xt extensions: use pr_<level> Jan Engelhardt
2010-03-19 14:47 ` Patrick McHardy [this message]
2010-03-19 14:50 ` nf-next: struct optimization, print changes Jan Engelhardt
2010-03-19 14:56 ` 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=4BA38E88.4080203@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.