From: Bjorn Andersson <andersson@kernel.org>
To: linux-pm@vger.kernel.org, konrad.dybcio@linaro.org,
viresh.kumar@linaro.org, ilia.lin@kernel.org, rafael@kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Robert Marko <robimarko@gmail.com>,
agross@kernel.org
Subject: Re: (subset) [PATCH 1/4] soc: qcom: socinfo: move SMEM item struct and defines to a header
Date: Fri, 26 May 2023 21:00:39 -0700 [thread overview]
Message-ID: <168516003597.405989.10506857474161773619.b4-ty@kernel.org> (raw)
In-Reply-To: <20230121112947.53433-1-robimarko@gmail.com>
On Sat, 21 Jan 2023 12:29:44 +0100, Robert Marko wrote:
> Move SMEM item struct and related defines to a header in order to be able
> to reuse them in the Qualcomm NVMEM CPUFreq driver instead of duplicating
> them.
>
>
Applied, thanks!
[1/4] soc: qcom: socinfo: move SMEM item struct and defines to a header
commit: ec001bb71e4476f7f5be9db693d5f43e65b9d8cb
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2023-05-27 3:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 11:29 [PATCH 1/4] soc: qcom: socinfo: move SMEM item struct and defines to a header Robert Marko
2023-01-21 11:29 ` [PATCH 2/4] cpufreq: qcom-nvmem: reuse socinfo SMEM item struct Robert Marko
2023-02-06 20:38 ` Bjorn Andersson
2023-02-07 4:15 ` Viresh Kumar
2023-01-21 11:29 ` [PATCH 3/4] cpufreq: qcom-nvmem: use SoC ID-s from bindings Robert Marko
2023-01-23 16:59 ` Konrad Dybcio
2023-02-06 20:40 ` Bjorn Andersson
2023-01-21 11:29 ` [PATCH 4/4] cpufreq: qcom-nvmem: make qcom_cpufreq_get_msm_id() return the SoC ID Robert Marko
2023-02-06 20:42 ` Bjorn Andersson
2023-02-18 14:43 ` Konrad Dybcio
2023-02-18 20:36 ` Dmitry Baryshkov
2023-02-18 20:40 ` Konrad Dybcio
2023-03-03 18:38 ` Robert Marko
2023-03-03 20:46 ` Konrad Dybcio
2023-03-03 21:38 ` Robert Marko
2023-03-03 21:40 ` Konrad Dybcio
2023-03-03 23:52 ` Dmitry Baryshkov
2023-01-21 11:33 ` [PATCH 1/4] soc: qcom: socinfo: move SMEM item struct and defines to a header Christophe JAILLET
2023-01-21 11:42 ` Robert Marko
2023-05-27 4:00 ` Bjorn Andersson [this message]
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=168516003597.405989.10506857474161773619.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=ilia.lin@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robimarko@gmail.com \
--cc=viresh.kumar@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.