linux-kernel - Re: linux-next: Fixes tag needs some work in the drm-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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <2145777.rZLEu8YqWI@diego>
Date:   Fri, 08 Feb 2019 12:31:38 +0100
From:   Heiko Stübner <heiko@...ech.de>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Dave Airlie <airlied@...ux.ie>,
        DRI <dri-devel@...ts.freedesktop.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Sandy Huang <hjc@...k-chips.com>
Subject: Re: linux-next: Fixes tag needs some work in the drm-fixes tree

Am Freitag, 8. Februar 2019, 12:01:37 CET schrieb Stephen Rothwell:
> Hi all,
> 
> In commit
> 
>   053ff09f1a8f ("drm/rockchip: rgb: update SPDX license identifier")
> 
> Fixes tag
> 
>   Fixes: 1f0f01515172 ("Add support for Rockchip Soc RGB output interface")
> 
> has these problem(s):
> 
>   - Subject does not match target commit subject

we had this warning already from the drm-misc-fixes tree :-) .

And the drm-* history is very much fixed (due to it being a shared tree)
so we'll probably have to live with that mistake I made (missing the
"drm/rockchip:" prefix from the subject). But as I said the other time,
it should hopefully be still be identifiable.


Heiko