From: Vinod Polimera <vpolimer@qti.qualcomm.com>
To: Javier Martinez Canillas <javierm@redhat.com>,
"dmitry.baryshkov@linaro.org" <dmitry.baryshkov@linaro.org>,
"Vinod Polimera (QUIC)" <quic_vpolimer@quicinc.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"freedreno@lists.freedesktop.org"
<freedreno@lists.freedesktop.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Cc: "dianders@chromium.org" <dianders@chromium.org>,
Abhinav Kumar <abhinavk@quicinc.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"swboyd@chromium.org" <swboyd@chromium.org>,
"Kalyan Thota (QUIC)" <quic_kalyant@quicinc.com>
Subject: RE: [v2] drm/msm: add null checks for drm device to avoid crash during probe defer
Date: Tue, 27 Sep 2022 09:41:43 +0000 [thread overview]
Message-ID: <BN0PR02MB81734C33B33066D5C4092CDAE4559@BN0PR02MB8173.namprd02.prod.outlook.com> (raw)
In-Reply-To: <2a3b6824-7a76-308c-c7a7-cc7c6001dfcb@redhat.com>
> -----Original Message-----
> From: Javier Martinez Canillas <javierm@redhat.com>
> Sent: Tuesday, September 27, 2022 2:33 PM
> To: Vinod Polimera <vpolimer@qti.qualcomm.com>;
> dmitry.baryshkov@linaro.org; Vinod Polimera (QUIC)
> <quic_vpolimer@quicinc.com>; dri-devel@lists.freedesktop.org; linux-arm-
> msm@vger.kernel.org; freedreno@lists.freedesktop.org;
> devicetree@vger.kernel.org
> Cc: dianders@chromium.org; vpolimer@quicinc.com; Abhinav Kumar
> <abhinavk@quicinc.com>; linux-kernel@vger.kernel.org;
> swboyd@chromium.org; kalyant@quicinc.com
> Subject: Re: [v2] drm/msm: add null checks for drm device to avoid crash
> during probe defer
>
> WARNING: This email originated from outside of Qualcomm. Please be wary
> of any links or attachments, and do not enable macros.
>
> Hello Vinod and Dmitry,
>
> On 9/27/22 09:31, Vinod Polimera wrote:
> >> -----Original Message-----
> >> From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> >> Sent: Friday, August 26, 2022 2:11 PM
> >> To: Vinod Polimera (QUIC) <quic_vpolimer@quicinc.com>; dri-
> >> devel@lists.freedesktop.org; linux-arm-msm@vger.kernel.org;
> >> freedreno@lists.freedesktop.org; devicetree@vger.kernel.org
> >> Cc: linux-kernel@vger.kernel.org; robdclark@gmail.com;
> >> dianders@chromium.org; vpolimer@quicinc.com;
> swboyd@chromium.org;
> >> kalyant@quicinc.com
> >> Subject: Re: [v2] drm/msm: add null checks for drm device to avoid crash
> >> during probe defer
> >>
>
> [...]
>
> >> Vinod, do we still want to pursue this fix? If so, could you please
> >> update it according to the comment.
> >>
>
> I don't think this patch is needed anymore, since AFAICT the issue has
> been fixed by commit 0a58d2ae572a ("drm/msm: Make .remove and
> .shutdown
> HW shutdown consistent") which is already in the drm/drm-next branch.
Yes , Issue will be fixed with the commit 0a58d2ae572a ("drm/msm: Make .remove and .shutdown) . Hence we can drop this patch.
>
> --
> Best regards,
>
> Javier Martinez Canillas
> Core Platforms
> Red Hat
- Vinod P.
prev parent reply other threads:[~2022-09-27 9:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 9:42 [v2] drm/msm: add null checks for drm device to avoid crash during probe defer Vinod Polimera
2022-06-03 9:44 ` Dmitry Baryshkov
2022-06-03 9:46 ` Dmitry Baryshkov
2022-06-15 12:20 ` Dmitry Baryshkov
2022-06-15 12:23 ` Dmitry Baryshkov
2022-08-26 8:41 ` Dmitry Baryshkov
2022-09-27 7:31 ` Vinod Polimera
2022-09-27 9:02 ` Javier Martinez Canillas
2022-09-27 9:41 ` Vinod Polimera [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=BN0PR02MB81734C33B33066D5C4092CDAE4559@BN0PR02MB8173.namprd02.prod.outlook.com \
--to=vpolimer@qti.qualcomm.com \
--cc=abhinavk@quicinc.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_kalyant@quicinc.com \
--cc=quic_vpolimer@quicinc.com \
--cc=swboyd@chromium.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 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).