From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH net-next 1/1] sip: introduce nf_nat_sip_hooks
Date: Mon, 30 Sep 2013 16:13:33 +0100 [thread overview]
Message-ID: <20130930151332.GA10721@macbook.localnet> (raw)
In-Reply-To: <20130930144951.GA13405@imap.eitzenberger.org>
On Mon, Sep 30, 2013 at 04:49:51PM +0200, Holger Eitzenberger wrote:
>
> > Thanks Holger, I wanted to do the same for a long time now. It actually
> > also fixes a minor race condition, when the NAT helper is loaded or
> > unloaded while a packet is processed the hooks may be invoked only
> > partially.
> >
> > Just one request:
> >
> > > +struct nf_nat_sip_hooks {
> > > + unsigned int (* nsh_msg)(struct sk_buff *skb,
> > > + unsigned int protoff,
> > > + unsigned int dataoff,
> > > + const char **dptr,
> > > + unsigned int *datalen);
> >
> > I really hate unpronouncable abbrevations, it hurts my eyes and IMO makes
> > it harder to read the code. Please use something nicer or get rid of the
> > prefix entirely.
>
> Ok, I'll remove the prefix then.
>
> However, personally I think they help grep'ing a lot, like e. g. the
> ndo_ prefix with netdevice ops (still usefull even as a 'cscope'
> user).
>
> Also the function names are *shorter* with the patch, as I was able
> to remove the nf_nat_ prefix.
Sure, its really just the unpronouncable thing, it makes it harder to
follow the code in your head. If you really want to keep the prefixes,
why not just use nat_sip_?
Cheers,
Patrick
prev parent reply other threads:[~2013-09-30 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 13:51 [PATCH net-next 0/1] sip: introduce nf_nat_sip_hooks Holger Eitzenberger
2013-09-30 13:51 ` [PATCH net-next 1/1] " Holger Eitzenberger
2013-09-30 14:03 ` Patrick McHardy
2013-09-30 14:49 ` Holger Eitzenberger
2013-09-30 15:13 ` 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=20130930151332.GA10721@macbook.localnet \
--to=kaber@trash.net \
--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.