Re: [dpdk-techboard] [PATCH] doc: update contribution guideline for dependent work

Hi,

On Mon, Dec 11, 2017 at 02:26:34PM +0000, Mcnamara, John wrote:

From: Yigit, Ferruh

quoted

Changing some part of the libraries but not updating all dependent code
cause maintenance problems.

...

Signed-off-by: Ferruh Yigit <redacted>

integration testing.

quoted

+* If changes effect other parts of the project, update all those parts as
well unless updating requires special knowledge.

I feel that "requiring special knowledge" is a bit blury. Shouldn't we add some
examples? Typically, I'm thinking about changes in ethdev that imply updating
the PMDs. Any opinion for this use case?