From: Markus Elfring <Markus.Elfring@web.de>
To: Yu Kuai <yukuai3@huawei.com>,
kernel@pengutronix.de, linux-arm-kernel@lists.infradead.org,
linux-imx@nxp.com
Cc: Anson Huang <Anson.Huang@nxp.com>,
Fabio Estevam <festevam@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>, Yi Zhang <yi.zhang@huawei.com>,
kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: imx6: add missing put_device() call in imx6q_suspend_init()
Date: Thu, 04 Jun 2020 19:07:55 +0000 [thread overview]
Message-ID: <cf810c93-297c-c02c-9bba-8c3d097b8e31@web.de> (raw)
In-Reply-To: <5acd7308-f6e1-4b1e-c744-bb2e5fdca1be@web.de>
> if of_find_device_by_node() succeed, imx6q_suspend_init() doesn't have a
> corresponding put_device(). Thus add a jump target to fix the exception
> handling for this function implementation.
Do you find a previous update suggestion useful?
ARM: imx6: Add missing put_device() call in imx6q_suspend_init()
https://lore.kernel.org/linux-arm-kernel/5acd7308-f6e1-4b1e-c744-bb2e5fdca1be@web.de/
https://lore.kernel.org/patchwork/patch/1151158/
https://lkml.org/lkml/2019/11/9/125
Regards,
Markus
next prev parent reply other threads:[~2020-06-04 19:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 15:30 [PATCH] ARM: imx6: Add missing put_device() call in imx6q_suspend_init() Markus Elfring
2020-06-04 19:07 ` Markus Elfring [this message]
2020-06-05 9:08 ` [PATCH] ARM: imx6: add " yukuai (C)
2020-06-05 10:15 ` Markus Elfring
2020-06-23 7:32 ` Shawn Guo
2020-06-23 7:48 ` Markus Elfring
2020-06-23 11:02 ` Shawn Guo
2020-06-23 12:00 ` Markus Elfring
2020-06-23 12:09 ` Shawn Guo
2020-06-23 12:28 ` Markus Elfring
2020-06-23 12:36 ` Shawn Guo
2020-06-23 14:33 ` Markus Elfring
2020-06-24 14:26 ` 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=cf810c93-297c-c02c-9bba-8c3d097b8e31@web.de \
--to=markus.elfring@web.de \
--cc=Anson.Huang@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.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;
as well as URLs for NNTP newsgroup(s).