[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAOf5uw=-AmHfw48csFQ_1U1Aj2B4yEAMoLT_-iHDC=EwALJwkA@mail.gmail.com>
Date: Tue, 17 May 2022 15:54:31 +0200
From: Michael Nazzareno Trimarchi <michael@...rulasolutions.com>
To: Fabio Estevam <festevam@...x.de>
Cc: Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
NXP Linux Team <linux-imx@....com>,
linux-amarula@...rulasolutions.com,
Rob Herring <robh+dt@...nel.org>,
"Ariel D'Alessandro" <ariel.dalessandro@...labora.com>,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
Simon Holesch <simon.holesch@...g.com>
Subject: Re: [PATCH] arm: dts: imx6ulz-bsh-smm-m2: Support proper board power off
Hi
On Tue, May 17, 2022 at 3:50 PM Fabio Estevam <festevam@...x.de> wrote:
>
> Hi Michael,
>
> On 17/05/2022 10:44, Michael Nazzareno Trimarchi wrote:
>
> >> You missed your own Signed-off-by tag here.
> >
> > It's fine, I can add Tested-by: Michael Trimarchi
> > <michael@...rulasolutions.com>
>
> If you are transmitting someone else's patch, then you need to add
> your own Signed-off-by to it.
>
> This is explained in Documentation/process/submitting-patches.rst:
>
> "Any further SoBs (Signed-off-by:'s) following the author's SoB are from
> people handling and transporting the patch, but were not involved in its
> development. SoB chains should reflect the **real** route a patch took
> as it was propagated to the maintainers and ultimately to Linus, with
> the first SoB entry signalling primary authorship of a single author."
Done, thank you
Michael
--
Michael Nazzareno Trimarchi
Co-Founder & Chief Executive Officer
M. +39 347 913 2170
michael@...rulasolutions.com
__________________________________
Amarula Solutions BV
Joop Geesinkweg 125, 1114 AB, Amsterdam, NL
T. +31 (0)85 111 9172
info@...rulasolutions.com
www.amarulasolutions.com
Powered by blists - more mailing lists