Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Caleb Connolly <caleb.connolly@linaro.org>,
	Jonathan Cameron <jic23@kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Rob Herring <robh+dt@kernel.org>, Andy Gross <agross@kernel.org>,
	Stephen Boyd <sboyd@kernel.org>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, sumit.semwal@linaro.org,
	amit.pundir@linaro.org, john.stultz@linaro.org,
	kernel test robot <lkp@intel.com>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH v8 2/9] mfd: qcom-spmi-pmic: expose the PMIC revid information to clients
Date: Fri, 25 Feb 2022 08:50:43 +0000	[thread overview]
Message-ID: <YhiYY/sXMvQ4VCZd@google.com> (raw)
In-Reply-To: <Yhft4zNcbD3ojN6i@builder.lan>

On Thu, 24 Feb 2022, Bjorn Andersson wrote:

> On Mon 21 Feb 16:07 CST 2022, Caleb Connolly wrote:
> 
> > Some PMIC functions such as the RRADC need to be aware of the PMIC
> > chip revision information to implement errata or otherwise adjust
> > behaviour, export the PMIC information to enable this.
> > 
> > This is specifically required to enable the RRADC to adjust
> > coefficients based on which chip fab the PMIC was produced in,
> > this can vary per unique device and therefore has to be read at
> > runtime.
> > 
> > [bugs in previous revision]
> > Reported-by: kernel test robot <lkp@intel.com>
> > Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> 
> This says is that "kernel test robot" and Dan reported that something
> needed to be fixed and this patch is the fix for this.
> 
> So even though their emails asks for you to give them credit like this
> you can't do it for new patches.

Right, or else you'd have to give credit to anyone who provided you
with a review.  This could potentially grow to quite a long list.

-- 
Lee Jones [李琼斯]
Principal Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2022-02-25  8:50 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21 22:07 [PATCH v8 0/9] iio: adc: introduce Qualcomm SPMI Round Robin ADC Caleb Connolly
2022-02-21 22:07 ` [PATCH v8 1/9] spmi: add a helper to look up an SPMI device from a device node Caleb Connolly
2022-02-26 17:03   ` Jonathan Cameron
2022-02-21 22:07 ` [PATCH v8 2/9] mfd: qcom-spmi-pmic: expose the PMIC revid information to clients Caleb Connolly
2022-02-24 20:43   ` Bjorn Andersson
2022-02-25  8:50     ` Lee Jones [this message]
2022-02-25  9:04       ` Dan Carpenter
2022-02-25  9:23         ` Lee Jones
2022-02-25  9:40           ` Dan Carpenter
2022-03-03  2:20             ` Caleb Connolly
2022-03-03  2:28               ` Philip Li
2022-03-03  9:05               ` Dan Carpenter
2022-03-03  9:52                 ` Lee Jones
2022-02-25 22:32         ` Bjorn Andersson
2022-02-26 17:11   ` Jonathan Cameron
2022-02-26 18:09   ` Dmitry Baryshkov
2022-02-28 18:08     ` Caleb Connolly
2022-02-28 18:57       ` Dmitry Baryshkov
2022-02-21 22:07 ` [PATCH v8 3/9] mfd: qcom-spmi-pmic: read fab id on supported PMICs Caleb Connolly
2022-02-21 22:07 ` [PATCH v8 4/9] dt-bindings: iio: adc: document qcom-spmi-rradc Caleb Connolly
2022-02-21 22:07 ` [PATCH v8 5/9] iio: adc: qcom-spmi-rradc: introduce round robin adc Caleb Connolly
2022-02-26 17:35   ` Jonathan Cameron
2022-02-26 17:36     ` Jonathan Cameron
2022-02-21 22:07 ` [PATCH v8 6/9] arm64: dts: qcom: pmi8998: add rradc node Caleb Connolly
2022-02-21 22:07 ` [PATCH v8 7/9] arm64: dts: qcom: sdm845-oneplus: enable rradc Caleb Connolly
2022-02-21 22:07 ` [PATCH v8 8/9] arm64: dts: qcom: sdm845-db845c: " Caleb Connolly
2022-02-21 22:07 ` [PATCH v8 9/9] arm64: dts: qcom: sdm845-xiaomi-beryllium: " Caleb Connolly

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=YhiYY/sXMvQ4VCZd@google.com \
    --to=lee.jones@linaro.org \
    --cc=agross@kernel.org \
    --cc=amit.pundir@linaro.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=caleb.connolly@linaro.org \
    --cc=dan.carpenter@oracle.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=john.stultz@linaro.org \
    --cc=lars@metafoo.de \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=sumit.semwal@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