From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: 20200622075956.171058-5-bjorn.andersson@linaro.org
Cc: linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Gross <agross@kernel.org>, Ohad Ben-Cohen <ohad@wizery.com>,
Baolin Wang <baolin.wang7@gmail.com>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2 4/4] arm64: dts: qcom: sm8250: Drop tcsr_mutex syscon
Date: Wed, 29 Dec 2021 07:42:19 -0800 [thread overview]
Message-ID: <YcyB21OI0GVhNmQJ@ripper> (raw)
In-Reply-To: <JWEO4R.7M77VCZXYS531@ixit.cz>
On Sat 25 Dec 06:57 PST 2021, David Heidelberg wrote:
> Hello,
>
> any particular reason, why you did applied this patch only to sm8250?
>
I was working on a 8250 board when this annoyed me, and I wanted to keep
the "example" clean so I only did that platform and then forgot to go
back and clean up the rest. (Same thing with the smem compatible moving
to reserved-memory).
> Is it safe to convert rest of tcsr-mutex nodes to new schema without
> additional testing?
>
I can't think of any reason it wouldn't be safe, so please feel free to
prepare a patch.
Thanks,
Bjorn
next prev parent reply other threads:[~2021-12-29 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-25 14:57 [PATCH v2 4/4] arm64: dts: qcom: sm8250: Drop tcsr_mutex syscon David Heidelberg
2021-12-29 15:42 ` Bjorn Andersson [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-22 7:59 [PATCH v2 0/4] hwspinlock: qcom: Allow dropping the intermediate TCSR mutex syscon Bjorn Andersson
2020-06-22 7:59 ` [PATCH v2 4/4] arm64: dts: qcom: sm8250: Drop tcsr_mutex syscon Bjorn Andersson
2020-07-15 19:36 ` Dmitry Baryshkov
2020-07-16 2:59 ` Manivannan Sadhasivam
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=YcyB21OI0GVhNmQJ@ripper \
--to=bjorn.andersson@linaro.org \
--cc=20200622075956.171058-5-bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=baolin.wang7@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.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