From: Johan Hovold <johan@kernel.org>
To: Abhinav Kumar <quic_abhinavk@quicinc.com>
Cc: Johan Hovold <johan+linaro@kernel.org>,
Douglas Anderson <dianders@chromium.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Rob Clark <robdclark@gmail.com>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <robert.foss@linaro.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>, Sean Paul <sean@poorly.run>,
Stephen Boyd <swboyd@chromium.org>,
Bjorn Andersson <andersson@kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Kuogee Hsieh <quic_khsieh@quicinc.com>,
Steev Klimaszewski <steev@kali.org>,
dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 09/10] drm/msm/dp: drop modeset sanity checks
Date: Wed, 28 Sep 2022 14:24:40 +0200 [thread overview]
Message-ID: <YzQ9CPwxZXFJCQGG@hovoldconsulting.com> (raw)
In-Reply-To: <d7688497-6229-40d4-3378-5036d699dfd7@quicinc.com>
On Tue, Sep 27, 2022 at 11:42:53AM -0700, Abhinav Kumar wrote:
> On 9/27/2022 12:14 AM, Johan Hovold wrote:
> > On Mon, Sep 26, 2022 at 11:17:20AM -0700, Abhinav Kumar wrote:
> >> On 9/13/2022 1:53 AM, Johan Hovold wrote:
> >>> Drop the overly defensive modeset sanity checks of function parameters
> >>> which have already been checked or used by the callers.
> >>>
> >>> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> >>> Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
> >>
> >> The change LGTM, hence
> >>
> >> Reviewed-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
> >>
> >> I think we can use below fixes tag so that we can pick up this entire
> >> series for the fixes cycle.
> >>
> >> Fixes: c943b4948b58 ("drm/msm/dp: add displayPort driver support")
> >
> > Perhaps that's a requirement for drm, but I wouldn't add a Fixes tag for
> > this otherwise as it's not a bug.
> >
> > You also have to watch out for Sasha and his autosel scripts which will
> > probably try to backport this to stable if it finds a Fixes tag.
> Discussed with Rob on IRC, we will apply everything except the last two
> patches of this series in the -fixes and take these two for the next
> kernel rev push.
So the fixes go in 6.0 and the two follow-on cleanups in 6.1? Or did you
mean 6.1 and 6.2?
Johan
next prev parent reply other threads:[~2022-09-28 12:24 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 8:53 [PATCH v2 00/10] drm/msm: probe deferral fixes Johan Hovold
2022-09-13 8:53 ` [PATCH v2 01/10] drm/msm: fix use-after-free on probe deferral Johan Hovold
2022-09-22 19:48 ` [Freedreno] " Kuogee Hsieh
2022-09-22 20:01 ` Kuogee Hsieh
2022-09-13 8:53 ` [PATCH v2 02/10] drm/msm/dp: fix memory corruption with too many bridges Johan Hovold
2022-09-22 19:51 ` [Freedreno] " Kuogee Hsieh
2022-09-22 19:54 ` Dmitry Baryshkov
2022-09-13 8:53 ` [PATCH v2 03/10] drm/msm/dsi: " Johan Hovold
2022-09-22 19:51 ` Kuogee Hsieh
2022-09-22 19:54 ` Dmitry Baryshkov
2022-09-13 8:53 ` [PATCH v2 04/10] drm/msm/hdmi: " Johan Hovold
2022-09-22 19:52 ` [Freedreno] " Kuogee Hsieh
2022-09-22 19:54 ` Dmitry Baryshkov
2022-09-13 8:53 ` [PATCH v2 05/10] drm/msm/dp: fix IRQ lifetime Johan Hovold
2022-09-22 19:54 ` [Freedreno] " Kuogee Hsieh
2022-09-13 8:53 ` [PATCH v2 06/10] drm/msm/dp: fix aux-bus EP lifetime Johan Hovold
2022-09-13 12:36 ` Doug Anderson
2022-09-13 8:53 ` [PATCH v2 07/10] drm/msm/dp: fix bridge lifetime Johan Hovold
2022-09-22 19:56 ` [Freedreno] " Kuogee Hsieh
2022-09-13 8:53 ` [PATCH v2 08/10] drm/msm/hdmi: fix IRQ lifetime Johan Hovold
2022-09-22 19:55 ` Kuogee Hsieh
2022-09-23 6:17 ` Johan Hovold
2022-09-13 8:53 ` [PATCH v2 09/10] drm/msm/dp: drop modeset sanity checks Johan Hovold
2022-09-22 19:57 ` Kuogee Hsieh
2022-09-26 18:17 ` Abhinav Kumar
2022-09-27 7:14 ` Johan Hovold
2022-09-27 18:42 ` Abhinav Kumar
2022-09-28 12:24 ` Johan Hovold [this message]
2022-09-28 15:33 ` Abhinav Kumar
2022-09-28 15:57 ` Johan Hovold
2022-09-13 8:53 ` [PATCH v2 10/10] drm/msm/dsi: " Johan Hovold
2022-09-22 19:58 ` [Freedreno] " Kuogee Hsieh
2022-09-26 18:21 ` Abhinav Kumar
2022-09-27 7:16 ` Johan Hovold
2022-09-27 18:44 ` Abhinav Kumar
2022-09-13 20:23 ` [PATCH v2 00/10] drm/msm: probe deferral fixes Steev Klimaszewski
2022-09-14 6:01 ` Johan Hovold
2022-09-16 16:43 ` Steev Klimaszewski
2022-09-20 9:06 ` Johan Hovold
2022-10-21 6:27 ` Johan Hovold
2022-10-21 16:05 ` Abhinav Kumar
2022-10-24 11:33 ` Johan Hovold
2022-10-24 15:01 ` Rob Clark
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=YzQ9CPwxZXFJCQGG@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=andersson@kernel.org \
--cc=andrzej.hajda@intel.com \
--cc=daniel@ffwll.ch \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=johan+linaro@kernel.org \
--cc=jonas@kwiboo.se \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_khsieh@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robert.foss@linaro.org \
--cc=sean@poorly.run \
--cc=steev@kali.org \
--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