From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Rob Clark <robdclark@gmail.com>,
Sean Paul <seanpaul@chromium.org>
Cc: Akhil P Oommen <quic_akhilpo@quicinc.com>,
Jiasheng Jiang <jiasheng@iscas.ac.cn>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Rob Clark <robdclark@chromium.org>
Subject: Re: linux-next: manual merge of the drm-msm-lumag tree with Linus', drm-msm trees
Date: Thu, 19 Jan 2023 13:03:15 +1100 [thread overview]
Message-ID: <20230119130315.766c9e71@canb.auug.org.au> (raw)
In-Reply-To: <20230119122350.2a767def@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1680 bytes --]
Hi all,
On Thu, 19 Jan 2023 12:23:50 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the drm-msm-lumag tree got a conflict in:
>
> drivers/gpu/drm/msm/msm_drv.c
>
> between commits:
>
> d73b1d02de08 ("drm/msm: Hangcheck progress detection")
> 8636500300a0 ("drm/msm: Fix failure paths in msm_drm_init()")
>
> from Linus', drm-msm trees and commit:
>
> 643b7d0869cc ("drm/msm: Add missing check and destroy for alloc_ordered_workqueue")
>
> from the drm-msm-lumag tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
Actually, the fixup was this:
f39d6f85acf03a184bb086cae8fd24d2c6d787fe
diff --cc drivers/gpu/drm/msm/msm_drv.c
index 0509e90d05e3,b052327181b2..d476c4ff0dd5
--- a/drivers/gpu/drm/msm/msm_drv.c
+++ b/drivers/gpu/drm/msm/msm_drv.c
@@@ -420,7 -418,11 +420,9 @@@ static int msm_drm_init(struct device *
priv->dev = ddev;
priv->wq = alloc_ordered_workqueue("msm", 0);
+ if (!priv->wq)
+ return -ENOMEM;
- priv->hangcheck_period = DRM_MSM_HANGCHECK_DEFAULT_PERIOD;
-
INIT_LIST_HEAD(&priv->objects);
mutex_init(&priv->obj_lock);
@@@ -542,8 -544,6 +544,7 @@@
err_msm_uninit:
msm_drm_uninit(dev);
- err_drm_dev_put:
+ drm_dev_put(ddev);
return ret;
}
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-01-19 2:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 1:23 linux-next: manual merge of the drm-msm-lumag tree with Linus', drm-msm trees Stephen Rothwell
2023-01-19 2:03 ` Stephen Rothwell [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=20230119130315.766c9e71@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dmitry.baryshkov@linaro.org \
--cc=jiasheng@iscas.ac.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=quic_akhilpo@quicinc.com \
--cc=robdclark@chromium.org \
--cc=robdclark@gmail.com \
--cc=seanpaul@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