From: Michal Simek <michal.simek@amd.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
"Appana Durga Kedareswara rao"
<appana.durga.kedareswara.rao@amd.com>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <michal.simek@xilinx.com>,
<derek.kiernan@xilinx.com>, <dragan.cvetic@xilinx.com>,
<arnd@arndb.de>, <gregkh@linuxfoundation.org>
Cc: <appanad@amd.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <git@amd.com>,
<git@xilinx.com>,
Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Subject: Re: [PATCH v2 3/4] dt-bindings: misc: tmr-inject: Add device-tree binding for TMR Inject
Date: Wed, 20 Jul 2022 14:35:04 +0200 [thread overview]
Message-ID: <713cf827-42a8-5164-2e60-7e8da10b91d1@amd.com> (raw)
In-Reply-To: <b2c4f548-449a-8855-fe68-005566711cae@linaro.org>
On 7/20/22 14:21, Krzysztof Kozlowski wrote:
> 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.
Good chat.
Cheers,
Michal
next prev parent reply other threads:[~2022-07-20 12:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 6:00 [PATCH v2 0/4] drivers: misc: Add support for TMR Manager and Inject IPs Appana Durga Kedareswara rao
2022-07-20 6:00 ` [PATCH v2 1/4] dt-bindings: misc: tmr-manager: Add device-tree binding for TMR Manager Appana Durga Kedareswara rao
2022-07-20 6:15 ` Krzysztof Kozlowski
2022-07-20 6:00 ` [PATCH v2 2/4] drivers: misc: Add Support " Appana Durga Kedareswara rao
2022-07-28 14:27 ` Greg KH
2022-07-29 8:13 ` Rao, Appana Durga Kedareswara
2022-07-20 6:00 ` [PATCH v2 3/4] dt-bindings: misc: tmr-inject: Add device-tree binding for TMR Inject Appana Durga Kedareswara rao
2022-07-20 6:15 ` Krzysztof Kozlowski
2022-07-20 8:26 ` Michal Simek
2022-07-20 9:35 ` Krzysztof Kozlowski
2022-07-20 12:09 ` Michal Simek
2022-07-20 12:21 ` Krzysztof Kozlowski
2022-07-20 12:35 ` Michal Simek [this message]
2022-07-20 13:21 ` Rao, Appana Durga Kedareswara
2022-07-20 6:00 ` [PATCH v2 4/4] drivers: misc: Add Support for TMR Inject IP Appana Durga Kedareswara rao
2022-07-28 14:24 ` Greg KH
2022-07-29 8:13 ` Rao, Appana Durga Kedareswara
2022-07-29 9:02 ` Greg KH
2022-08-03 6:35 ` Rao, Appana Durga Kedareswara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=713cf827-42a8-5164-2e60-7e8da10b91d1@amd.com \
--to=michal.simek@amd.com \
--cc=appana.durga.kedareswara.rao@amd.com \
--cc=appana.durga.rao@xilinx.com \
--cc=appanad@amd.com \
--cc=arnd@arndb.de \
--cc=derek.kiernan@xilinx.com \
--cc=devicetree@vger.kernel.org \
--cc=dragan.cvetic@xilinx.com \
--cc=git@amd.com \
--cc=git@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).