From: Markus Elfring <Markus.Elfring@web.de>
To: Wolfram Sang <wsa@kernel.org>,
linux-pm@vger.kernel.org, kernel@pengutronix.de,
linux-imx@nxp.com, linux-i2c@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: Aisheng Dong <aisheng.dong@nxp.com>,
Dinghao Liu <dinghao.liu@zju.edu.cn>,
Ulf Hansson <ulf.hansson@linaro.org>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Andy Duan <fugang.duan@nxp.com>,
linux-kernel@vger.kernel.org, Qiushi Wu <wu000273@umn.edu>,
Navid Emamdoost <emamd001@umn.edu>, Kangjie Lu <kjlu@umn.edu>,
Aditya Pakki <pakki001@umn.edu>
Subject: Re: [v3] i2c: imx-lpi2c: Fix runtime PM imbalance on error
Date: Mon, 15 Jun 2020 09:40:53 +0200 [thread overview]
Message-ID: <44768ceb-ee7c-85f2-6091-ec6bcd06ab54@web.de> (raw)
In-Reply-To: <20200615070613.GA1497@kunai>
> I started a seperate thread:
>
> https://lkml.org/lkml/2020/6/14/76
>
> Still, on-going discussion if the proper fix is to remove the error check.
I find that a bit of additional information can make such a link safer.
RFC: a failing pm_runtime_get increases the refcnt?
https://lore.kernel.org/lkml/20200614090751.GA2878@kunai/
How will the clarification of corresponding software aspects evolve further?
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: Markus Elfring <Markus.Elfring@web.de>
To: Wolfram Sang <wsa@kernel.org>,
linux-pm@vger.kernel.org, kernel@pengutronix.de,
linux-imx@nxp.com, linux-i2c@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: Aisheng Dong <aisheng.dong@nxp.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Andy Duan <fugang.duan@nxp.com>, Qiushi Wu <wu000273@umn.edu>,
Fabio Estevam <festevam@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Kangjie Lu <kjlu@umn.edu>,
linux-kernel@vger.kernel.org, Navid Emamdoost <emamd001@umn.edu>,
Dinghao Liu <dinghao.liu@zju.edu.cn>,
Aditya Pakki <pakki001@umn.edu>, Shawn Guo <shawnguo@kernel.org>
Subject: Re: [v3] i2c: imx-lpi2c: Fix runtime PM imbalance on error
Date: Mon, 15 Jun 2020 09:40:53 +0200 [thread overview]
Message-ID: <44768ceb-ee7c-85f2-6091-ec6bcd06ab54@web.de> (raw)
In-Reply-To: <20200615070613.GA1497@kunai>
> I started a seperate thread:
>
> https://lkml.org/lkml/2020/6/14/76
>
> Still, on-going discussion if the proper fix is to remove the error check.
I find that a bit of additional information can make such a link safer.
RFC: a failing pm_runtime_get increases the refcnt?
https://lore.kernel.org/lkml/20200614090751.GA2878@kunai/
How will the clarification of corresponding software aspects evolve further?
Regards,
Markus
_______________________________________________
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:[~2020-06-15 7:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 6:16 [PATCH] [v3] i2c: imx-lpi2c: Fix runtime PM imbalance on error Dinghao Liu
2020-06-01 6:16 ` Dinghao Liu
2020-06-01 6:24 ` [EXT] " Andy Duan
2020-06-01 6:24 ` Andy Duan
2020-06-01 6:42 ` [PATCH v3] i2c: imx-lpi2c: Fix runtime PM imbalance in lpi2c_imx_master_enable() Markus Elfring
2020-06-01 6:42 ` Markus Elfring
2020-06-01 6:42 ` Markus Elfring
2020-06-14 9:12 ` [PATCH] [v3] i2c: imx-lpi2c: Fix runtime PM imbalance on error Wolfram Sang
2020-06-14 9:12 ` Wolfram Sang
2020-06-14 12:08 ` dinghao.liu
2020-06-14 12:08 ` dinghao.liu
2020-06-15 6:33 ` Aisheng Dong
2020-06-15 6:33 ` Aisheng Dong
2020-06-15 7:06 ` Wolfram Sang
2020-06-15 7:06 ` Wolfram Sang
2020-06-15 7:40 ` Markus Elfring [this message]
2020-06-15 7:40 ` Markus Elfring
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=44768ceb-ee7c-85f2-6091-ec6bcd06ab54@web.de \
--to=markus.elfring@web.de \
--cc=aisheng.dong@nxp.com \
--cc=dinghao.liu@zju.edu.cn \
--cc=emamd001@umn.edu \
--cc=festevam@gmail.com \
--cc=fugang.duan@nxp.com \
--cc=kernel@pengutronix.de \
--cc=kjlu@umn.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pakki001@umn.edu \
--cc=rafael.j.wysocki@intel.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=wsa@kernel.org \
--cc=wu000273@umn.edu \
/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.