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] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210729122521.GM4670@sirena.org.uk>
Date:   Thu, 29 Jul 2021 13:25:21 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Christian König <christian.koenig@....com>
Cc:     Rob Clark <robdclark@...il.com>, Sean Paul <seanpaul@...omium.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Rob Clark <robdclark@...omium.org>
Subject: Re: linux-next: manual merge of the drm-msm tree with the drm-next
 tree

On Thu, Jul 29, 2021 at 01:44:42PM +0200, Christian König wrote:
> Am 29.07.21 um 13:10 schrieb Mark Brown:
> > Hi all,
> > 
> > Today's linux-next merge of the drm-msm tree got a conflict in:
> > 
> >    drivers/gpu/drm/msm/msm_gem.c
> > 
> > between commit:
> > 
> >    60f800b2bdfa ("drm/msm: always wait for the exclusive fence")
> > 
> > from the drm-next tree and commit:
> > 
> >    1d8a5ca436ee ("drm/msm: Conversion to drm scheduler")
> > 
> > from the drm-msm 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/msm/msm_gem.c
> > index 39c35414d7b5,5db07fc287ad..000000000000
> > --- a/drivers/gpu/drm/msm/msm_gem.c
> > +++ b/drivers/gpu/drm/msm/msm_gem.c
> 
> thanks for the fixup, but something went wrong here. The diff is just empty.
> 
> Any idea what's going on?

The change modified a function that is simply deleted so the resulting
diff was empty.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ