From: Harald Welte <laforge@netfilter.org>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Netfilter Core Team <coreteam@netfilter.org>,
James Morris <jmorris@intercode.com.au>,
Andrew Morton <akpm@osdl.org>, Patrick McHardy <kaber@trash.net>
Subject: Re: [PATCH] Decrease number of pointer derefs in nfnetlink_queue.c
Date: Fri, 9 Dec 2005 10:34:50 +0530 [thread overview]
Message-ID: <20051209050450.GF4244@rama.exocore.com> (raw)
In-Reply-To: <200512082336.01678.jesper.juhl@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
On Thu, Dec 08, 2005 at 11:36:01PM +0100, Jesper Juhl wrote:
> Here's a small patch to decrease the number of pointer derefs in
> net/netfilter/nfnetlink_queue.c
Thanks, the patch looks fine to me.
Also, if you feel like it, I would recommend doing a similar patch for
nfnetlink_log (which has a similar architecture to nfnetlink_queue).
Patrick: Please merge into your queue of pending patches, unless you
have any objections. Thanks!
--
- Harald Welte <laforge@netfilter.org> http://netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-12-09 4:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 22:36 [PATCH] Decrease number of pointer derefs in nfnetlink_queue.c Jesper Juhl
2005-12-08 22:51 ` David S. Miller
2005-12-08 23:10 ` Jesper Juhl
2005-12-08 23:56 ` Steven Rostedt
2005-12-09 0:08 ` Jeff Garzik
2005-12-09 5:04 ` Harald Welte [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=20051209050450.GF4244@rama.exocore.com \
--to=laforge@netfilter.org \
--cc=akpm@osdl.org \
--cc=coreteam@netfilter.org \
--cc=jesper.juhl@gmail.com \
--cc=jmorris@intercode.com.au \
--cc=kaber@trash.net \
--cc=linux-kernel@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.