All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics <intel-gfx@lists.freedesktop.org>,
	DRI <dri-devel@lists.freedesktop.org>,
	Dave Airlie <airlied@linux.ie>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: manual merge of the drm-misc tree with the drm-intel tree
Date: Fri, 21 Jul 2017 10:11:48 +1000	[thread overview]
Message-ID: <20170721101148.4b20f55e@canb.auug.org.au> (raw)
In-Reply-To: <20170720112333.010b9ac8@canb.auug.org.au>

Hi all,

The following conflict now exists between the drm and drm-intel trees.

On Thu, 20 Jul 2017 11:23:33 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the drm-misc tree got a conflict in:
> 
>   drivers/gpu/drm/i915/i915_drv.c
> 
> between commit:
> 
>   99c539bef538 ("drm/i915: unregister interfaces first in unload")
> 
> from the drm-intel tree and commit:
> 
>   baf54385af78 ("drm/i915: Drop drm_vblank_cleanup")
> 
> from the drm-misc 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.
> 
> -- 
> Cheers,
> Stephen Rothwell
> 
> diff --cc drivers/gpu/drm/i915/i915_drv.c
> index f406aec8a499,04d9bd84ee43..000000000000
> --- a/drivers/gpu/drm/i915/i915_drv.c
> +++ b/drivers/gpu/drm/i915/i915_drv.c
> @@@ -1386,8 -1367,8 +1384,6 @@@ void i915_driver_unload(struct drm_devi
>   
>   	intel_gvt_cleanup(dev_priv);
>   
> - 	drm_vblank_cleanup(dev);
>  -	i915_driver_unregister(dev_priv);
> --
>   	intel_modeset_cleanup(dev);
>   
>   	/*

-- 
Cheers,
Stephen Rothwell

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics <intel-gfx@lists.freedesktop.org>,
	DRI <dri-devel@lists.freedesktop.org>,
	Dave Airlie <airlied@linux.ie>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: manual merge of the drm-misc tree with the drm-intel tree
Date: Fri, 21 Jul 2017 10:11:48 +1000	[thread overview]
Message-ID: <20170721101148.4b20f55e@canb.auug.org.au> (raw)
In-Reply-To: <20170720112333.010b9ac8@canb.auug.org.au>

Hi all,

The following conflict now exists between the drm and drm-intel trees.

On Thu, 20 Jul 2017 11:23:33 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the drm-misc tree got a conflict in:
> 
>   drivers/gpu/drm/i915/i915_drv.c
> 
> between commit:
> 
>   99c539bef538 ("drm/i915: unregister interfaces first in unload")
> 
> from the drm-intel tree and commit:
> 
>   baf54385af78 ("drm/i915: Drop drm_vblank_cleanup")
> 
> from the drm-misc 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.
> 
> -- 
> Cheers,
> Stephen Rothwell
> 
> diff --cc drivers/gpu/drm/i915/i915_drv.c
> index f406aec8a499,04d9bd84ee43..000000000000
> --- a/drivers/gpu/drm/i915/i915_drv.c
> +++ b/drivers/gpu/drm/i915/i915_drv.c
> @@@ -1386,8 -1367,8 +1384,6 @@@ void i915_driver_unload(struct drm_devi
>   
>   	intel_gvt_cleanup(dev_priv);
>   
> - 	drm_vblank_cleanup(dev);
>  -	i915_driver_unregister(dev_priv);
> --
>   	intel_modeset_cleanup(dev);
>   
>   	/*

-- 
Cheers,
Stephen Rothwell
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-07-21  0:11 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-20  1:23 linux-next: manual merge of the drm-misc tree with the drm-intel tree Stephen Rothwell
2017-07-21  0:11 ` Stephen Rothwell [this message]
2017-07-21  0:11   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2020-09-22  3:34 Stephen Rothwell
2020-09-22  3:34 ` Stephen Rothwell
2020-04-15  1:52 Stephen Rothwell
2020-04-15  1:52 ` Stephen Rothwell
2019-08-20  2:19 Stephen Rothwell
2019-05-22 23:58 Stephen Rothwell
2019-05-22 23:53 Stephen Rothwell
2019-03-19  0:51 Stephen Rothwell
2019-01-16  1:27 Stephen Rothwell
2019-01-16  1:27 ` Stephen Rothwell
2017-05-23  2:00 Stephen Rothwell
2017-05-25  1:53 ` Stephen Rothwell
2017-05-25  1:53   ` Stephen Rothwell
2017-03-06 23:48 Stephen Rothwell
2017-03-06 23:48 ` Stephen Rothwell
2017-01-03  2:14 Stephen Rothwell
2017-01-03  2:08 Stephen Rothwell
2017-01-03  1:59 Stephen Rothwell
2017-01-03  1:50 Stephen Rothwell
2016-10-23 23:59 Stephen Rothwell
2016-05-03  3:24 Stephen Rothwell
2016-05-03  3:24 ` Stephen Rothwell
2016-05-03  7:54 ` Daniel Vetter
2016-05-03  7:54   ` Daniel Vetter
2016-04-27  2:32 Stephen Rothwell
2016-04-27  2:32 ` Stephen Rothwell
2015-12-14  1:06 Stephen Rothwell
2015-12-14  1:06 ` Stephen Rothwell
2015-10-15  2:04 Stephen Rothwell
2015-10-15  2:04 ` Stephen Rothwell
2015-09-29  1:26 Stephen Rothwell
2015-09-29  1:26 ` Stephen Rothwell

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=20170721101148.4b20f55e@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.