From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Russell King <linux@armlinux.org.uk>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v4 1/5] ARM: qcom_defconfig: enable more Qualcomm drivers
Date: Wed, 27 Jul 2022 10:21:45 +0300 [thread overview]
Message-ID: <CAA8EJpr_aW6_+4SXun3FsWtA+sy6zRnbzK7A6FRH5jM0VzFCcA@mail.gmail.com> (raw)
In-Reply-To: <20220727065830.10681-2-krzysztof.kozlowski@linaro.org>
On Wed, 27 Jul 2022 at 09:58, Krzysztof Kozlowski
<krzysztof.kozlowski@linaro.org> wrote:
>
> Enable Qualcomm drivers:
> 1. socinfo driver to provide some basic information about the
> SoC being used.
> 2. Remote filesystem memory driver (used in MSM8974).
> 3. RPM Power domain (used in MSM8226).
> 4. Sleep stats driver (used in MSM8916, MSM8974 and APQ8084).
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
--
With best wishes
Dmitry
next prev parent reply other threads:[~2022-07-27 7:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 6:58 [PATCH v4 0/5] ARM: qcom: defconfig: socinfo + cleanup Krzysztof Kozlowski
2022-07-27 6:58 ` [PATCH v4 1/5] ARM: qcom_defconfig: enable more Qualcomm drivers Krzysztof Kozlowski
2022-07-27 7:21 ` Dmitry Baryshkov [this message]
2022-07-27 6:58 ` [PATCH v4 2/5] ARM: multi_v7_defconfig: " Krzysztof Kozlowski
2022-07-27 7:22 ` Dmitry Baryshkov
2022-07-27 6:58 ` [PATCH v4 3/5] arm64: defconfig: " Krzysztof Kozlowski
2022-07-27 6:58 ` [PATCH v4 4/5] ARM: qcom: include defconfig in MAINTAINERS Krzysztof Kozlowski
2022-07-27 6:58 ` [PATCH v4 5/5] ARM: qcom_defconfig: order items with savedefconfig Krzysztof Kozlowski
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=CAA8EJpr_aW6_+4SXun3FsWtA+sy6zRnbzK7A6FRH5jM0VzFCcA@mail.gmail.com \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).