From: classabbyamp <dev@placeviolette.net>
To: dmitry.baryshkov@linaro.org
Cc: alexeymin@postmarketos.org, andersson@kernel.org,
bryan.odonoghue@linaro.org, johan+linaro@kernel.org,
konrad.dybcio@linaro.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-remoteproc@vger.kernel.org,
mathieu.poirier@linaro.org, neil.armstrong@linaro.org,
quic_sibis@quicinc.com, steev@kali.org, wuxilin123@gmail.com
Subject: Re: [PATCH v8 0/5] soc: qcom: add in-kernel pd-mapper implementation
Date: Thu, 30 May 2024 18:39:47 -0400 [thread overview]
Message-ID: <00a76167-6d25-4c5a-b5a5-e61104b74147@placeviolette.net> (raw)
In-Reply-To: <20240512-qcom-pd-mapper-v8-0-5ecbb276fcc0@linaro.org>
I've tested this applied on top of kernel 6.8.11 on an X13s over the
past week and it's been working well.
--
classabbyamp
next prev parent reply other threads:[~2024-05-30 22:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 21:56 [PATCH v8 0/5] soc: qcom: add in-kernel pd-mapper implementation Dmitry Baryshkov
2024-05-11 21:56 ` [PATCH v8 1/5] soc: qcom: pdr: protect locator_addr with the main mutex Dmitry Baryshkov
2024-06-05 22:48 ` Chris Lew
2024-06-06 9:15 ` Dmitry Baryshkov
2024-05-11 21:56 ` [PATCH v8 2/5] soc: qcom: pdr: fix parsing of domains lists Dmitry Baryshkov
2024-06-06 0:39 ` Chris Lew
2024-05-11 21:56 ` [PATCH v8 3/5] soc: qcom: pdr: extract PDR message marshalling data Dmitry Baryshkov
2024-05-11 21:56 ` [PATCH v8 4/5] soc: qcom: add pd-mapper implementation Dmitry Baryshkov
2024-06-08 0:45 ` Chris Lew
2024-05-11 21:56 ` [PATCH v8 5/5] remoteproc: qcom: enable in-kernel PD mapper Dmitry Baryshkov
2024-06-08 0:46 ` Chris Lew
2024-05-13 3:23 ` [PATCH v8 0/5] soc: qcom: add in-kernel pd-mapper implementation Steev Klimaszewski
2024-05-30 22:39 ` classabbyamp [this message]
2024-06-06 9:47 ` Neil Armstrong
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=00a76167-6d25-4c5a-b5a5-e61104b74147@placeviolette.net \
--to=dev@placeviolette.net \
--cc=alexeymin@postmarketos.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=johan+linaro@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_sibis@quicinc.com \
--cc=steev@kali.org \
--cc=wuxilin123@gmail.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