From: Igor Plyatov <plyatov@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Zhang Rui <rui.zhang@intel.com>,
Eduardo Valentin <edubezval@gmail.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Amit Kucheria <amit.kucheria@verdurent.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
linux-pm@vger.kernel.org,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Issue with imx_get_temp()
Date: Tue, 3 Dec 2019 17:34:46 +0300 [thread overview]
Message-ID: <edcbf5f1-7d77-a384-6746-02154cbf497c@gmail.com> (raw)
In-Reply-To: <CAOMZO5Aoj9pUpMdqVTG2pOUBUpnHsxA-Kduhia7_EJZvdEGjwQ@mail.gmail.com>
Dear Fabio,
> Are you able to reproduce this issue with a 5.4.1 kernel?
Sorry, I can test currently only with 5.1.1.
Best wishes.
--
Igor Plyatov
WARNING: multiple messages have this Message-ID (diff)
From: Igor Plyatov <plyatov@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Amit Kucheria <amit.kucheria@verdurent.com>,
linux-pm@vger.kernel.org, Sascha Hauer <s.hauer@pengutronix.de>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Eduardo Valentin <edubezval@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Zhang Rui <rui.zhang@intel.com>, Shawn Guo <shawnguo@kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Issue with imx_get_temp()
Date: Tue, 3 Dec 2019 17:34:46 +0300 [thread overview]
Message-ID: <edcbf5f1-7d77-a384-6746-02154cbf497c@gmail.com> (raw)
In-Reply-To: <CAOMZO5Aoj9pUpMdqVTG2pOUBUpnHsxA-Kduhia7_EJZvdEGjwQ@mail.gmail.com>
Dear Fabio,
> Are you able to reproduce this issue with a 5.4.1 kernel?
Sorry, I can test currently only with 5.1.1.
Best wishes.
--
Igor Plyatov
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-12-03 14:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <de442143-568d-5fbf-ed0c-d169e33e5d66@gmail.com>
2019-12-02 13:49 ` Issue with imx_get_temp() Fabio Estevam
2019-12-02 13:49 ` Fabio Estevam
2019-12-03 14:34 ` Igor Plyatov [this message]
2019-12-03 14:34 ` Igor Plyatov
2019-12-02 13:45 Igor Plyatov
2019-12-02 13:45 ` Igor Plyatov
2019-12-02 16:06 ` Christoph Niedermaier
2019-12-03 10:15 ` Marco Felsch
2019-12-03 10:15 ` Marco Felsch
2019-12-03 12:04 ` Fabio Estevam
2019-12-03 12:04 ` Fabio Estevam
2019-12-03 13:13 ` Fabio Estevam
2019-12-03 13:13 ` Fabio Estevam
2019-12-03 14:36 ` Igor Plyatov
2019-12-03 14:36 ` Igor Plyatov
2019-12-10 12:19 ` Fabio Estevam
2019-12-10 12:19 ` Fabio Estevam
2020-01-09 12:17 ` Fabio Estevam
2020-01-09 12:17 ` Fabio Estevam
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=edcbf5f1-7d77-a384-6746-02154cbf497c@gmail.com \
--to=plyatov@gmail.com \
--cc=amit.kucheria@verdurent.com \
--cc=daniel.lezcano@linaro.org \
--cc=edubezval@gmail.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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 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.