From: Patrick McHardy <kaber@trash•net>
To: Jiri Pirko <jpirko@redhat•com>
Cc: Eric Dumazet <eric.dumazet@gmail•com>,
netdev@vger•kernel.org, netfilter-devel@vger•kernel.org,
netfilter@vger•kernel.org, davem@davemloft•net,
Krzysztof Oledzki <ole@ans•pl>
Subject: Re: [net-next-2.6 PATCH] netfilter: ctnetlink: compute message size properly
Date: Thu, 01 Apr 2010 12:50:23 +0200 [thread overview]
Message-ID: <4BB47A6F.8000804@trash.net> (raw)
In-Reply-To: <20100401104356.GD2879@psychotron.redhat.com>
Jiri Pirko wrote:
> Thu, Apr 01, 2010 at 12:40:23PM CEST, kaber@trash•net wrote:
>> Eric Dumazet wrote:
>>> Le mercredi 31 mars 2010 à 20:21 +0200, Jiri Pirko a écrit :
>>>> Okay, I see your point. How about this:
>>>>
>>>> Subject: [net-next-2.6 PATCH] netfilter: ctnetlink: compute message size properly V2
>>>>
>>>> Message size should be dependent on net->ct.sysctl_acct, not on
>>>> CONFIG_NF_CT_ACCT definition.
>>>>
>>> Then Changelog is not updated with the actual test :)
>> I've fixed up the changelog and applied the patch, thanks.
>
> Cand I ask on which tree?
Since this doesn't confirm to Dave's definition of crucial fixes,
I've applied it to nf-next-2.6.git :)
git://git.kernel.org/pub/scm/linux/kernel/git/kaber/nf-next-2.6.git
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger•kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-04-01 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 15:11 [net-next-2.6 PATCH] netfilter: ctnetlink: compute message size properly Jiri Pirko
2010-03-31 17:46 ` Patrick McHardy
2010-03-31 18:21 ` Jiri Pirko
2010-03-31 18:35 ` Eric Dumazet
2010-04-01 10:40 ` Patrick McHardy
2010-04-01 10:43 ` Jiri Pirko
2010-04-01 10:50 ` 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=4BB47A6F.8000804@trash.net \
--to=kaber@trash$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=jpirko@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=netfilter-devel@vger$(echo .)kernel.org \
--cc=netfilter@vger$(echo .)kernel.org \
--cc=ole@ans$(echo .)pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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