From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: [PATCH 1/7] Remove debugging messages from nfnetlink
Date: Tue, 13 Feb 2007 11:46:57 +0100 [thread overview]
Message-ID: <45D19721.2050209@trash.net> (raw)
In-Reply-To: <45D0EE1F.6060400@netfilter.org>
This doesn't apply, it seems like you generated the patches
against a kernel tree without Yoshifuji's whitespace cleanup.
Please rediff and resend (the faster the better if we want
to get this in 2.6.21). I'll just comment on the patches for
now.
Pablo Neira Ayuso wrote:
> [PATCH] Remove debugging messages from nfnetlink
>
> Remove early debugging messages from nfnetlink
Looks good, I'll also happily apply similar patches for other
netfilter files.
prev parent reply other threads:[~2007-02-13 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-12 22:45 [PATCH 1/7] Remove debugging messages from nfnetlink Pablo Neira Ayuso
2007-02-13 10:46 ` 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=45D19721.2050209@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pablo@netfilter.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).