From: Sasha Levin <sashal@kernel.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: stable@vger.kernel.org, architt@codeaurora.org,
a.hajda@samsung.com, Laurent.pinchart@ideasonboard.com,
airlied@linux.ie, jsarha@ti.com, tomi.valkeinen@ti.com,
vinholikatti@gmail.com, jejb@linux.vnet.ibm.com,
martin.petersen@oracle.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [BACKPORT 4.19.y 3/3] drm/tilcdc: Register cpufreq notifier after we have initialized crtc
Date: Thu, 29 Aug 2019 19:11:09 -0400 [thread overview]
Message-ID: <20190829231109.GR5281@sasha-vm> (raw)
In-Reply-To: <20190829200001.17092-4-mathieu.poirier@linaro.org>
On Thu, Aug 29, 2019 at 02:00:01PM -0600, Mathieu Poirier wrote:
>From: Jyri Sarha <jsarha@ti.com>
>
>commit 432973fd3a20102840d5f7e61af9f1a03c217a4c upstream
>
>Register cpufreq notifier after we have initialized the crtc and
>unregister it before we remove the ctrc. Receiving a cpufreq notify
>without crtc causes a crash.
>
>Reported-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
>Signed-off-by: Jyri Sarha <jsarha@ti.com>
>Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
I've queued this one for 4.19 and 4.14, thank you!
--
Thanks,
Sasha
prev parent reply other threads:[~2019-08-29 23:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 19:59 [BACKPORT 4.19.y 0/3] Candidate from TI 4.19 product kernel Mathieu Poirier
2019-08-29 19:59 ` [BACKPORT 4.19.y 1/3] drm/bridge: tfp410: fix memleak in get_modes() Mathieu Poirier
2019-08-29 23:01 ` Sasha Levin
2019-08-29 20:00 ` [BACKPORT 4.19.y 2/3] scsi: ufs: Fix RX_TERMINATION_FORCE_ENABLE define value Mathieu Poirier
2019-08-29 23:06 ` Sasha Levin
2019-08-29 20:00 ` [BACKPORT 4.19.y 3/3] drm/tilcdc: Register cpufreq notifier after we have initialized crtc Mathieu Poirier
2019-08-29 23:11 ` Sasha Levin [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=20190829231109.GR5281@sasha-vm \
--to=sashal@kernel.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=airlied@linux.ie \
--cc=architt@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=jsarha@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mathieu.poirier@linaro.org \
--cc=stable@vger.kernel.org \
--cc=tomi.valkeinen@ti.com \
--cc=vinholikatti@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