linux-kernel - Re: linux-next: Signed-off-by missing for commits in the drm-intel-fixes 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 for Android: free password hash cracker in your pocket

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

Message-ID: <157676106618.16538.6275487528140541951@jlahtine-desk.ger.corp.intel.com>
Date:   Thu, 19 Dec 2019 15:11:06 +0200
From:   Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>
To:     DRI <dri-devel@...ts.freedesktop.org>,
        Daniel Vetter <daniel.vetter@...ll.ch>,
        Intel Graphics <intel-gfx@...ts.freedesktop.org>,
        Jani Nikula <jani.nikula@...ux.intel.com>,
        Rodrigo Vivi <rodrigo.vivi@...el.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commits in the drm-intel-fixes tree

Quoting Jani Nikula (2019-12-19 14:37:02)
> On Thu, 19 Dec 2019, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> > Hi all,
> >
> > Commits
> >
> >   987e379d7500 ("Revert "devtmpfs: use do_mount() instead of ksys_mount()"")
> >   9bd5ba4fe25a ("Revert "initrd: use do_mount() instead of ksys_mount()"")
> >   fa31001c96ad ("Revert "init: use do_mount() instead of ksys_mount()"")
> >
> > are missing a Signed-off-by from their author and committer.
> >
> > Reverts are commits too and should have reasonable commit messages.
> 
> Confused. I can't find said commits. And can't fathom why they'd be in
> any drm-intel tree.

Sorry. A glitch in the matrix, as our CI farm is hit by -rc2
regressions. I did the usual trick of pushing the reverts/fixes on top
of drm-intel-fixes to get CI pick them up for a run to get results, and
then proceeded to immediately remove them.

I imagine that if the commit messages got scanned, they get propagated
somewhere else too? Feel free to drop that HEAD completely.

If this is a big inconvenience, we can look into other ways of adding
the patches on top of drm-intel-fixes to get CI working when there
are regressions during -rc1/-rc2.

Regards, Joonas