From: Vinod Koul <vkoul@kernel.org>
To: Vaishali Thakkar <vaishali.thakkar@linaro.org>
Cc: agross@kernel.org, david.brown@linaro.org,
gregkh@linuxfoundation.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, rafael@kernel.org,
bjorn.andersson@linaro.org
Subject: Re: [PATCH v6 0/5] soc: qcom: Add SoC info driver
Date: Wed, 24 Jul 2019 09:58:19 +0530 [thread overview]
Message-ID: <20190724042819.GG12733@vkoul-mobl.Dlink> (raw)
In-Reply-To: <20190723223515.27839-1-vaishali.thakkar@linaro.org>
On 24-07-19, 04:05, Vaishali Thakkar wrote:
> This patchset adds SoC info driver which can provide information
> such as Chip ID, Chip family and serial number about Qualcomm SoCs
> to user space via sysfs. Furthermore, it allows userspace to get
> information about custom attributes and various image version
> information via debugfs.
>
> The patchset cleanly applies on top of v5.2-rc7.
And on v5.3-rc1 :) and I have tested this on db845c, seems to work fine
for me
Tested-by: Vinod Koul <vkoul@kernel.org>
--
~Vinod
prev parent reply other threads:[~2019-07-24 4:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 22:35 [PATCH v6 0/5] soc: qcom: Add SoC info driver Vaishali Thakkar
2019-07-23 22:35 ` [PATCH v6 1/5] base: soc: Add serial_number attribute to soc Vaishali Thakkar
2019-07-24 4:26 ` Vinod Koul
2019-07-23 22:35 ` [PATCH v6 2/5] base: soc: Export soc_device_register/unregister APIs Vaishali Thakkar
2019-07-23 22:35 ` [PATCH v6 3/5] soc: qcom: Add socinfo driver Vaishali Thakkar
2019-07-24 4:27 ` Vinod Koul
2019-07-23 22:35 ` [PATCH v6 4/5] soc: qcom: socinfo: Expose custom attributes Vaishali Thakkar
2019-07-24 4:27 ` Vinod Koul
2019-07-23 22:35 ` [PATCH v6 5/5] soc: qcom: socinfo: Expose image information Vaishali Thakkar
2019-07-24 4:27 ` Vinod Koul
2019-07-24 4:28 ` Vinod Koul [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=20190724042819.GG12733@vkoul-mobl.Dlink \
--to=vkoul@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=vaishali.thakkar@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 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).