linux-kernel - Re: linux-next: Fixes tag needs some work in the cpufreq-arm 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: <20190118053802.rm7fc5z7wk3agc2f@vireshk-i7>
Date:   Fri, 18 Jan 2019 11:08:02 +0530
From:   Viresh Kumar <viresh.kumar@...aro.org>
To:     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>,
        Lukas Bulwahn <lukas.bulwahn@...il.com>
Subject: Re: linux-next: Fixes tag needs some work in the cpufreq-arm tree

On 18-01-19, 16:33, Stephen Rothwell wrote:
> Hi Viresh,
> 
> In commit
> 
>   3ca12c96ef5e ("MAINTAINERS: use common indentation")
> 
> Fixes tag
> 
>   Fixes: 46e2856b8e188949757c9123fd7f9ce36edd1a52
> 
> Fixes tags should be in this format:
> 
>   Fixes: 46e2856b8e18 ("cpufreq: Add Kryo CPU scaling driver")

Fixed and pushed again.

I missed looking into that. You must be running some sort of sanity
checks on the branch itself, can I know what exactly are you doing so
that I can try the same.

-- 
viresh