[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170714080316.vlqgtao3fznpsuur@nataraja>
Date: Fri, 14 Jul 2017 10:03:16 +0200
From: Harald Welte <laforge@...monks.org>
To: Jiannan Ouyang <ouyangj@...com>
Cc: "osmocom-net-gprs@...ts.osmocom.org"
<osmocom-net-gprs@...ts.osmocom.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"dev@...nvswitch.org" <dev@...nvswitch.org>,
"pablo@...filter.org" <pablo@...filter.org>,
"pshelar@...ira.com" <pshelar@...ira.com>,
"wieger.ijntema.tno@...il.com" <wieger.ijntema.tno@...il.com>,
"yi.y.yang@...el.com" <yi.y.yang@...el.com>,
"joe@....org" <joe@....org>,
Amar Padmanabhan <amarpadmanabhan@...com>
Subject: Re: [PATCH net-next v1 1/3] gtp: refactor to support flow-based gtp
encap and decap
Hi Jiannan,
> > > gtp = netdev_priv(dev);
> > > + gtp->net = src_net;
> >ยท
> > Isn't this a generic change that's independent of your work on OVS GTP?
>
> It is meant to be OVS independent. What makes it not? Should I leave
> this field un-initialized?
In general, in all FOSS projects I have worked (and particularly the
Linux kernel), it is a strict rule that any given patch adresses only
one logical change. So if your change is for flow-based "OVS" support
in the GTP code, and the "gtp->net = src_net" is a generic change (and
not something specifically required by flow/OVS) then it should be a
separate patch. Similarly to the cosmetic changes which should be a
separate patch.
--
- 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