All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Jones <rob.jones@codethink.co.uk>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, linux-kernel@codethink.co.uk
Subject: Re: [PATCH] net/netfilter/x_tables.c: use __seq_open_private()
Date: Tue, 23 Sep 2014 16:32:39 +0100	[thread overview]
Message-ID: <54219297.2060906@codethink.co.uk> (raw)
In-Reply-To: <20140923140237.GA27307@salvia>

Would you like that change made and re-submitted? It's the work of
moments to do it.

I was only concentrating on not changing the logic so I didn't check on
whether and existing initialisation was made redundant.

On 23/09/14 15:02, Pablo Neira Ayuso wrote:
> On Fri, Sep 19, 2014 at 11:27:51AM +0100, Rob Jones wrote:
>> Reduce boilerplate code by using __seq_open_private() instead of seq_open()
>> in xt_match_open() and xt_target_open().
>>
>> Signed-off-by: Rob Jones <rob.jones@codethink.co.uk>
>> ---
>>
>> This patch uses an existing variant of seq_open() to reduce the kernel code
>> size.
>
> Less code to maintain, good.
>
>> The only significant variation from the pre-existing code is the fact that
>> __seq_open_private() calls kzalloc() rather than kmalloc(), which could
>> conceivably have an impact on timing.
>
> I think you can skip
>
>          trav->class = MTTG_TRAV_INIT;
>
> too, now that trav is set to zero.
>
>
>

-- 
Rob Jones
Codethink Ltd
mailto:rob.jones@codethink.co.uk
tel:+44 161 236 5575

  reply	other threads:[~2014-09-23 15:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19 10:27 [PATCH] net/netfilter/x_tables.c: use __seq_open_private() Rob Jones
2014-09-23 14:02 ` Pablo Neira Ayuso
2014-09-23 15:32   ` Rob Jones [this message]
2014-09-23 15:36     ` Pablo Neira Ayuso
2014-09-23 15:38       ` Rob Jones
  -- strict thread matches above, loose matches on Subject: below --
2014-09-18 16:48 Rob Jones
2014-09-18 17:51 ` Lars Dam

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=54219297.2060906@codethink.co.uk \
    --to=rob.jones@codethink.co.uk \
    --cc=linux-kernel@codethink.co.uk \
    --cc=netfilter-devel@vger.kernel.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 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.