On Mon, Sep 09, 2019 at 11:44:15AM +0100, James Bottomley wrote:

> I haven't really found corporations attempting to apply pressure to get
> their patches merged as is, although I've heard of others having this

I've definitely faced this in various forms, mostly coming from
companies in the embedded space.  It feels like it's got better
over time as companies have become less prone to going on
substantial out of tree adventures but it's still there.

> problem.  My usual problem is that the creator of the patch is deeply
> wedded to their design and doesn't want to change so it's an individual
> rather than a corporate issue.

That's often a corporate problem as well, if the company has a
big investment in whatever approach or codebase they have they
may not want to spend the time on substantial rework.  Often it
seems fairly clear that the people doing the upstreaming have
inherited something from other engineers rather than having done
the design and original implementation themselves.  In my more
embedded experience I'd say that the corporate investment is a
more common issue than developers.

I'm not sure I have any particularly bright ideas other than
being clear with people about what the issues are and asking for
clearer explanations of what's being done and why it's different
to everything else.