[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b2c4f548-449a-8855-fe68-005566711cae@linaro.org>
Date: Wed, 20 Jul 2022 14:21:54 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Michal Simek <michal.simek@....com>,
Appana Durga Kedareswara rao
<appana.durga.kedareswara.rao@....com>, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, michal.simek@...inx.com,
derek.kiernan@...inx.com, dragan.cvetic@...inx.com, arnd@...db.de,
gregkh@...uxfoundation.org
Cc: appanad@....com, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
git@....com, git@...inx.com,
Appana Durga Kedareswara rao <appana.durga.rao@...inx.com>
Subject: Re: [PATCH v2 3/4] dt-bindings: misc: tmr-inject: Add device-tree
binding for TMR Inject
On 20/07/2022 14:09, Michal Simek wrote:
>> Similarly when you change jobs while resending your patch - you do not
>> add new SoB but just keep SoB from @previous-company.com.
>
> IMHO That would be more questionable when you create changes in origin series
> and new employer pays you to do the work.
True, when changes happen in between, it gets tricky.
> If it is 3rd party company picking series where upstreaming is not finished you
> will expect that 3rd party will add their sob lines there too.
Of course, because this is different person. The SoB comes always from a
person, although he might represent company.
Best regards,
Krzysztof
Powered by blists - more mailing lists