Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1409763 > unrolled thread
| Started by | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| First post | 2016-05-31 03:10 +0200 |
| Last post | 2016-05-31 03:10 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
linux-next: manual merge of the drm-intel tree with Linus' tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-05-31 03:10 +0200
| From | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| Date | 2016-05-31 03:10 +0200 |
| Subject | linux-next: manual merge of the drm-intel tree with Linus' tree |
| Message-ID | <rEGlY-3Nt-3@gated-at.bofh.it> |
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in:
drivers/gpu/drm/i915/intel_display.c
between commit:
9bd18728a3f2 ("drm/i915: Ignore stale wm register values on resume on ilk-bdw (v2)")
from Linus' tree and commit:
e3d5457c7caa ("drm/i915: Ignore stale wm register values on resume on ilk-bdw (v2)")
from the drm-intel tree.
I fixed it up (I used teh drm-intel tree version) 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
Back to top | Article view | linux.kernel
csiph-web