From: Jonathan Cameron <jic23@kernel.org>
To: Alexandre Mergnat <amergnat@baylibre.com>
Cc: ChiaEn Wu <chiaen_wu@richtek.com>,
lars@metafoo.de, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.com,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, peterwu.pub@gmail.com,
cy_huang@richtek.com
Subject: Re: [PATCH v3] iio: adc: mt6370: Fix ibus and ibat scaling value of some specific vendor ID chips
Date: Wed, 12 Apr 2023 21:36:42 +0100 [thread overview]
Message-ID: <20230412213642.1a942f64@jic23-huawei> (raw)
In-Reply-To: <d2667a9d-20bf-bda2-9d69-4f5000db1633@baylibre.com>
On Wed, 12 Apr 2023 13:31:06 +0200
Alexandre Mergnat <amergnat@baylibre.com> wrote:
> On 10/04/2023 12:34, ChiaEn Wu wrote:
> > The scale value of ibus and ibat on the datasheet is incorrect due to the
> > customer report after the experimentation with some specific vendor ID
> > chips.
> >
> > Fixes: c1404d1b659f ("iio: adc: mt6370: Add MediaTek MT6370 support")
> > Signed-off-by: ChiaEn Wu<chiaen_wu@richtek.com>
>
> Reviewed-by: Alexandre Mergnat <amergnat@baylibre.com>
>
Applied to the fixes-togreg branch of iio.git and marked for stable.
As we are very late in this cycle I may well drag this into the
queue for the coming merge window as it will land upstream slightly
quicker that way. If not it will go upstream early in next cycle.
As it's been broken for a while I'm not going to rush this upstream.
Jonathan
prev parent reply other threads:[~2023-04-12 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 10:34 [PATCH v3] iio: adc: mt6370: Fix ibus and ibat scaling value of some specific vendor ID chips ChiaEn Wu
2023-04-12 11:31 ` Alexandre Mergnat
2023-04-12 20:36 ` Jonathan Cameron [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=20230412213642.1a942f64@jic23-huawei \
--to=jic23@kernel.org \
--cc=amergnat@baylibre.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chiaen_wu@richtek.com \
--cc=cy_huang@richtek.com \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=peterwu.pub@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