From: Nishanth Menon <nm@ti.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
Bao Cheng Su <baocheng.su@siemens.com>,
Benedikt Niedermayr <benedikt.niedermayr@siemens.com>
Subject: Re: [PATCH 4/7] arm64: dts: ti: iot2050: Refactor the m.2 and minipcie power pin
Date: Fri, 27 Oct 2023 08:55:08 -0500 [thread overview]
Message-ID: <20231027135508.2up657g74muvhz6t@favoring> (raw)
In-Reply-To: <110c4e57-adab-4211-9d8f-4603a5e5e756@siemens.com>
On 15:45-20231027, Jan Kiszka wrote:
> On 27.10.23 15:43, Nishanth Menon wrote:
> > On 15:34-20231027, Jan Kiszka wrote:
> >> From: Su Bao Cheng <baocheng.su@siemens.com>
> >>
> >> Make the m.2 power control pin also available on miniPCIE variants.
> >>
> >> This can fix some miniPCIE card hang issue, by forcing a power on reset
> >> during boot.
> >>
> >> Signed-off-by: Baocheng Su <baocheng.su@siemens.com>
> >> ---
> >
> > Jan - please Sign-off for the carried chain..
> >
>
> Sure, can do. Was intentionally not doing that because I somewhere
> picked up that this is not desired.
Hmm... Documentation/process/submitting-patches.rst
Signed-off-by: must always be that of the developer submitting the
patch. --> I assume you are this ;).
Signed-off-by: First Co-Author <first@coauthor.example.org>
Signed-off-by: Second Co-Author <second@coauthor.example.org>
Signed-off-by: From Author <from@author.example.org>
Signed-off-by: Random Co-Author <random@coauthor.example.org>
Signed-off-by: From Author <from@author.example.org>
Signed-off-by: Submitting Co-Author <sub@coauthor.example.org>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2023-10-27 13:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 13:34 [PATCH 0/7] arm64: dts: iot2050: DT fixes, cleanups and enhancements Jan Kiszka
2023-10-27 13:34 ` [PATCH 1/7] arm64: dts: ti: iot2050: Re-add aliases Jan Kiszka
2023-10-27 13:34 ` [PATCH 2/7] arm64: dts: ti: iot2050: Drop unused ecap0 PWM Jan Kiszka
2023-10-27 13:34 ` [PATCH 3/7] arm64: dts: ti: iot2050: Definitions for runtime pinmuxing Jan Kiszka
2023-10-27 13:44 ` Nishanth Menon
2023-10-27 13:34 ` [PATCH 4/7] arm64: dts: ti: iot2050: Refactor the m.2 and minipcie power pin Jan Kiszka
2023-10-27 13:43 ` Nishanth Menon
2023-10-27 13:45 ` Jan Kiszka
2023-10-27 13:55 ` Nishanth Menon [this message]
2023-10-27 13:34 ` [PATCH 5/7] dt-bindings: trivial-devices: Add IOT2050 Arduino SPI connector Jan Kiszka
2023-10-30 16:43 ` Rob Herring
2023-10-30 17:35 ` Jan Kiszka
2023-10-27 13:34 ` [PATCH 6/7] arm64: dts: ti: iot2050: Add node for SPI devices on Arduino connector Jan Kiszka
2023-10-27 13:34 ` [PATCH 7/7] arm64: dts: ti: iot2050: Add icssg-prueth nodes for PG2 devices Jan Kiszka
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=20231027135508.2up657g74muvhz6t@favoring \
--to=nm@ti.com \
--cc=baocheng.su@siemens.com \
--cc=benedikt.niedermayr@siemens.com \
--cc=devicetree@vger.kernel.org \
--cc=jan.kiszka@siemens.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).