Hi Greg,
Today's linux-next merge of the staging tree got a conflict in
drivers/gpu/drm/Makefile between commit
955b12def42e83287c1bdb1411d99451753c1391 ("drm: Convert proc files to
seq_file and introduce debugfs") from the drm tree and commit
69a914df73e04807248f21b6738dab9cf9e3c094 ("drm: Add a tracker for global
objects") from the staging tree.
Just trivial overlapping additions. I fixed it up (see below) and can
carry the fix as necessary.
However, I do need to wonder why changes to drivers/gpu are appearing in
the staging tree - I assumed that its updates would be restricted to the
drivers/staging directory (as much as possible).
--
Cheers,
Stephen Rothwell sfr@xxxxxxxxxxxxxxxx
http://www.canb.auug.org.au/~sfr/
diff --cc drivers/gpu/drm/Makefile
index 4ec5061,9186cfd..0000000
--- a/drivers/gpu/drm/Makefile
+++ b/drivers/gpu/drm/Makefile
@@@ -11,7 -11,7 +11,7 @@@ drm-y := drm_auth.o drm_bufs.o dr
drm_agpsupport.o drm_scatter.o ati_pcigart.o drm_pci.o \
drm_sysfs.o drm_hashtab.o drm_sman.o drm_mm.o \
drm_crtc.o drm_crtc_helper.o drm_modes.o drm_edid.o \
- drm_info.o drm_debugfs.o
- drm_global.o
++ drm_info.o drm_debugfs.o drm_global.o
drm-$(CONFIG_COMPAT) += drm_ioc32.o
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
