From: Konrad Dybcio <konrad.dybcio@somainline.org>
To: Yassine Oudjana <y.oudjana@protonmail.com>
Cc: "angelogioacchino.delregno@somainline.org"
<angelogioacchino.delregno@somainline.org>,
"marijn.suijten@somainline.org" <marijn.suijten@somainline.org>,
"agross@kernel.org" <agross@kernel.org>,
"bjorn.andersson@linaro.org" <bjorn.andersson@linaro.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 08/11] arm64: dts: qcom: pm8994: Add RESIN node
Date: Wed, 3 Mar 2021 21:33:17 +0100 [thread overview]
Message-ID: <c7e3394a-9cfa-ad9b-8d62-14d7151c54ea@somainline.org> (raw)
In-Reply-To: <-8dygFkqlPLCYtnwUWBLrCubmjkNhno40CBzzZ2tmlWdpJC1Ihmoe1dpMSvsgoBQ58Idh2v_rBHNEQLIwpTRtpndQm_8nSarmkXlZo975CU=@protonmail.com>
On 03.03.2021 17:43, Yassine Oudjana wrote:
> In-Reply-To: <20210228130831.203765-8-konrad.dybcio@somainline.org>
>
> I've sent a similar patch[1] a while ago, although I didn't disable resin by default:
> https://lore.kernel.org/lkml/BmEPgqFMiMXOzn9xFz6KSPtOZdWoeJ8zUpGXI_p7U9FBBSgbG2IP6AkuvbWWzy7MVuBkrhOas158Vd9klSLFmrbSRGEpQGouiAFpsf03Ag=@protonmail.com/
>
> Yassine
I'm totally fine with applying Yassine's patch with a `status = "disabled";` line added instead (we don't want RESIN on all devices!).
Konrad
next prev parent reply other threads:[~2021-03-04 0:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 16:43 [PATCH 08/11] arm64: dts: qcom: pm8994: Add RESIN node Yassine Oudjana
2021-03-03 20:33 ` Konrad Dybcio [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-02-28 13:08 [PATCH 01/11] arm64: dts: qcom: msm8996: Sanitize pins Konrad Dybcio
2021-02-28 13:08 ` [PATCH 08/11] arm64: dts: qcom: pm8994: Add RESIN node Konrad Dybcio
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=c7e3394a-9cfa-ad9b-8d62-14d7151c54ea@somainline.org \
--to=konrad.dybcio@somainline.org \
--cc=agross@kernel.org \
--cc=angelogioacchino.delregno@somainline.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=robh+dt@kernel.org \
--cc=y.oudjana@protonmail.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).