[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1516124800.96408.1486995289464.JavaMail.zimbra@tpip.net>
Date: Mon, 13 Feb 2017 15:14:49 +0100 (CET)
From: Andreas Schultz <aschultz@...p.net>
To: laforge <laforge@...monks.org>
Cc: pablo <pablo@...filter.org>, netdev <netdev@...r.kernel.org>,
Lionel Gauthier <Lionel.Gauthier@...ecom.fr>,
openbsc <openbsc@...ts.osmocom.org>
Subject: Re: [PATCH net-next v2 4/6] gtp: consolidate pdp context
destruction into helper
----- On Feb 6, 2017, at 2:58 PM, laforge laforge@...monks.org wrote:
> Hi Andreas,
>
> On Mon, Jan 30, 2017 at 05:37:11PM +0100, Andreas Schultz wrote:
>> Consolidate duplicate code into helper.
>
> Makes complete sense.
>
> However:
>
>> +static void pdp_context_delete(struct pdp_ctx *pctx);
>> +
>
> why introduce the forward-declaration and then define the function
> further down in the file? I think in general, it is preferred to put
> helper functions on top, before their first use, so forward declarations
> can be avoided? Particularly if the helper function doesn't call any
> other functions that are not yet declared at this point.
I wanted to keep functions that work on the data structure close
together. I this case the function the initialized the pdp context
and the delete function for it.
Andreas
>
> Please note the above might just be my personal taste, not sure if
> that's a general habit in the kernel networking code these days.
>
> So with or without the re-ordering:
>
> Acked-by: Harald Welte <laforge@...monks.org>
>
> --
> - Harald Welte <laforge@...monks.org> http://laforge.gnumonks.org/
> ============================================================================
> "Privacy in residential applications is a desirable marketing option."
> (ETSI EN 300 175-7 Ch. A6)
Powered by blists - more mailing lists