linux-kernel - Re: linux-next: manual merge of the char-misc tree with the drm-intel tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 11 Nov 2021 10:05:59 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Dave Airlie <airlied@...ux.ie>
Cc:     Greg KH <greg@...ah.com>, Arnd Bergmann <arnd@...db.de>,
        Daniel Vetter <daniel.vetter@...ll.ch>,
        Jani Nikula <jani.nikula@...ux.intel.com>,
        Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>,
        Rodrigo Vivi <rodrigo.vivi@...el.com>,
        Intel Graphics <intel-gfx@...ts.freedesktop.org>,
        DRI <dri-devel@...ts.freedesktop.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Matthew Auld <matthew.auld@...el.com>
Subject: Re: linux-next: manual merge of the char-misc tree with the
 drm-intel tree

Hi all,

On Fri, 5 Nov 2021 12:51:22 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> On Thu, 28 Oct 2021 18:27:53 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> > 
> > Today's linux-next merge of the char-misc tree got a conflict in:
> > 
> >   drivers/gpu/drm/i915/gem/i915_gem_dmabuf.c
> > 
> > between commit:
> > 
> >   5740211ea442 ("drm/i915/dmabuf: fix broken build")
> > 
> > from the drm-intel tree and commit:
> > 
> >   16b0314aa746 ("dma-buf: move dma-buf symbols into the DMA_BUF module namespace")
> > 
> > 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.
> > 
> > diff --cc drivers/gpu/drm/i915/gem/i915_gem_dmabuf.c
> > index a45d0ec2c5b6,abb854281347..000000000000
> > --- a/drivers/gpu/drm/i915/gem/i915_gem_dmabuf.c
> > +++ b/drivers/gpu/drm/i915/gem/i915_gem_dmabuf.c
> > @@@ -12,13 -13,8 +13,15 @@@
> >   #include "i915_gem_object.h"
> >   #include "i915_scatterlist.h"
> >   
> >  +#if defined(CONFIG_X86)
> >  +#include <asm/smp.h>
> >  +#else
> >  +#define wbinvd_on_all_cpus() \
> >  +	pr_warn(DRIVER_NAME ": Missing cache flush in %s\n", __func__)
> >  +#endif
> >  +
> > + MODULE_IMPORT_NS(DMA_BUF);
> > + 
> >   I915_SELFTEST_DECLARE(static bool force_different_devices;)
> >   
> >   static struct drm_i915_gem_object *dma_buf_to_obj(struct dma_buf *buf)  
> 
> This is now a conflict between the drm-intel tree and Linux' tree.

This is now a conflict between the drm tree and Linus' tree.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped