From: Pavel Emelyanov <xemul@openvz.org>
To: Patrick McHardy <kaber@trash.net>
Cc: David Miller <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>,
devel@openvz.org
Subject: Re: [PATCH 1/2][NETFILTER] Consolidate nf_sockopt and compat_nf_sockopt
Date: Fri, 02 Nov 2007 14:07:26 +0300 [thread overview]
Message-ID: <472B04EE.6030705@openvz.org> (raw)
In-Reply-To: <472B02A1.40601@trash.net>
Patrick McHardy wrote:
> Pavel Emelyanov wrote:
>> Both lookup the nf_sockopt_ops object to call the get/set callbacks
>> from, but they perform it in a completely similar way.
>>
>> Introduce the helper for finding the ops.
>>
>> Signed-off-by: Pavel Emelyanov <xemul@openvz.org >
>
>
> This conflicts with a cleanup patch from Alexey Dobriyan. I'll
> push it upstream today, please resend after rediffing. Thanks.
>
Amazing :) Alexey's patch does the same thing as my 2nd
one does :) I will resend this one :)
Thanks,
Pavel
prev parent reply other threads:[~2007-11-02 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 15:55 [PATCH 1/2][NETFILTER] Consolidate nf_sockopt and compat_nf_sockopt Pavel Emelyanov
2007-11-02 10:57 ` Patrick McHardy
2007-11-02 11:07 ` Pavel Emelyanov [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=472B04EE.6030705@openvz.org \
--to=xemul@openvz.org \
--cc=davem@davemloft.net \
--cc=devel@openvz.org \
--cc=kaber@trash.net \
--cc=netdev@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).