[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181017142257.5002799b@canb.auug.org.au>
Date: Wed, 17 Oct 2018 14:22:57 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Greg KH <greg@...ah.com>, Arnd Bergmann <arnd@...db.de>,
Dave Airlie <airlied@...ux.ie>,
DRI <dri-devel@...ts.freedesktop.org>
Cc: Linux-Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Gerd Hoffmann <kraxel@...hat.com>,
Dan Williams <dan.j.williams@...el.com>,
Alexander Viro <viro@...iv.linux.org.uk>
Subject: linux-next: manual merge of the char-misc tree with the drm tree
Hi all,
Today's linux-next merge of the char-misc tree got a conflict in:
MAINTAINERS
between commit:
fbb0de795078 ("Add udmabuf misc device")
from the drm tree and commit:
9793c1fd1775 ("MAINTAINERS: Clarify UIO vs UIOVEC maintainer")
from the char-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 MAINTAINERS
index 7d70a6c5eeee,a38c13c7da9a..000000000000
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@@ -15594,14 -15365,12 +15595,20 @@@ F: arch/x86/um
F: fs/hostfs/
F: fs/hppfs/
+ USERSPACE COPYIN/COPYOUT (UIOVEC)
+ M: Alexander Viro <viro@...iv.linux.org.uk>
+ S: Maintained
+ F: lib/iov_iter.c
+ F: include/linux/uio.h
+
+USERSPACE DMA BUFFER DRIVER
+M: Gerd Hoffmann <kraxel@...hat.com>
+S: Maintained
+L: dri-devel@...ts.freedesktop.org
+F: drivers/dma-buf/udmabuf.c
+F: include/uapi/linux/udmabuf.h
+T: git git://anongit.freedesktop.org/drm/drm-misc
+
USERSPACE I/O (UIO)
M: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
S: Maintained
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists