public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics <intel-gfx@lists.freedesktop.org>,
	DRI <dri-devel@lists.freedesktop.org>,
	Dave Airlie <airlied@linux.ie>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Sam Ravnborg <sam@ravnborg.org>,
	Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: linux-next: manual merge of the drm-misc tree with the drm tree
Date: Fri, 8 Feb 2019 09:53:33 +0100	[thread overview]
Message-ID: <20190208085333.GH23159@phenom.ffwll.local> (raw)
In-Reply-To: <20190208122744.4a63bec0@canb.auug.org.au>

On Fri, Feb 08, 2019 at 12:27:44PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next merge of the drm-misc tree got a conflict in:
> 
>   drivers/gpu/drm/i915/intel_display.c
> 
> between commit:
> 
>   9f58892ea996 ("drm/i915: Pull all the reset functionality together into i915_reset.c")
> 
> from the drm tree and commit:
> 
>   d0e93599d396 ("drm/i915: prepare for drmP.h removal from drm_modeset_helper.h")
> 
> from the drm-misc tree.
> 
> I fixed it up (I think I got the right include files in the right order in
> the end - see below and please check the final result) 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.

There isn't a "below" afaics ....
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

  reply	other threads:[~2019-02-08  8:53 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08  1:27 linux-next: manual merge of the drm-misc tree with the drm tree Stephen Rothwell
2019-02-08  8:53 ` Daniel Vetter [this message]
2019-02-08  9:25   ` Stephen Rothwell
2019-02-08  9:34     ` Daniel Vetter
  -- strict thread matches above, loose matches on Subject: below --
2026-04-03 13:34 Mark Brown
2026-03-30 16:02 Mark Brown
2026-03-30 16:02 Mark Brown
2025-07-01  3:07 Stephen Rothwell
2025-07-01  3:21 ` Stephen Rothwell
2022-11-09 23:54 Stephen Rothwell
2019-10-09  0:12 Stephen Rothwell
2019-10-09  0:10 Stephen Rothwell
2019-10-08 23:46 Stephen Rothwell
2019-10-08 23:38 Stephen Rothwell
2019-10-08 23:33 Stephen Rothwell
2019-08-19  3:18 Stephen Rothwell
2019-06-11  3:52 Stephen Rothwell
2019-06-11  3:38 Stephen Rothwell
2019-04-09  1:34 Stephen Rothwell
2019-04-09  7:23 ` Gerd Hoffmann
2018-11-23  0:13 Stephen Rothwell
2018-09-18  1:31 Stephen Rothwell
2018-09-12  0:39 Stephen Rothwell
2018-03-19  1:29 Stephen Rothwell
2018-03-19 14:14 ` Ville Syrjälä
2017-11-01  3:36 Stephen Rothwell
2017-04-03  3:18 Stephen Rothwell
2016-09-28  2:11 Stephen Rothwell
2014-12-10  1:49 Stephen Rothwell
2014-12-03  2:43 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=20190208085333.GH23159@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@linux.ie \
    --cc=chris@chris-wilson.co.uk \
    --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 \
    --cc=sam@ravnborg.org \
    --cc=sfr@canb.auug.org.au \
    /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