From: Fabio Estevam <festevam@denx.de>
To: Michael Nazzareno Trimarchi <michael@amarulasolutions.com>
Cc: Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
linux-amarula@amarulasolutions.com,
Rob Herring <robh+dt@kernel.org>,
Ariel D'Alessandro <ariel.dalessandro@collabora.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Simon Holesch <simon.holesch@bshg.com>
Subject: Re: [PATCH] arm: dts: imx6ulz-bsh-smm-m2: Support proper board power off
Date: Tue, 17 May 2022 10:50:34 -0300 [thread overview]
Message-ID: <7e434e2426ab61476e5f58db764cbd9f@denx.de> (raw)
In-Reply-To: <CAOf5uw=QxFM=CCFLZ=fZCfn9BBz1aFpkPQuED1uHxHRABwMHMQ@mail.gmail.com>
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@amarulasolutions.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."
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-05-17 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 13:35 [PATCH] arm: dts: imx6ulz-bsh-smm-m2: Support proper board power off Michael Trimarchi
2022-05-17 13:41 ` Fabio Estevam
2022-05-17 13:44 ` Michael Nazzareno Trimarchi
2022-05-17 13:50 ` Fabio Estevam [this message]
2022-05-17 13:54 ` Michael Nazzareno Trimarchi
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=7e434e2426ab61476e5f58db764cbd9f@denx.de \
--to=festevam@denx.de \
--cc=ariel.dalessandro@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@amarulasolutions.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=simon.holesch@bshg.com \
/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