linux-kernel - Re: linux-next: Fixes tag needs some work in the clk 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]

Date:   Wed, 16 Jan 2019 14:35:59 -0800
From:   Stephen Boyd <sboyd@...nel.org>
To:     Mike Turquette <mturquette@...libre.com>,
        Stephen Boyd <sboyd@...eaurora.org>,
        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>,
        Dinh Nguyen <dinguyen@...nel.org>,
        Paul Gortmaker <paul.gortmaker@...driver.com>
Subject: Re: linux-next: Fixes tag needs some work in the clk tree

Quoting Stephen Rothwell (2019-01-15 13:34:40)
> [I am experimenting with checking the Fixes tags in commits in linux-next.
> Please let me know if you think I am being too strict.]
> 
> Hi all,
> 
> Commit
> 
>   b488517b28a4 ("clk: socfpga: stratix10: fix naming convention for the fixed-clocks")
> 
> has a malformed Fixes tag:
> 
>   Fixes: 07afb8db7340 ("clk: socfpga: stratix10: add clock driver for
>   Stratix10 platform")
> 
> It should not be split over 2 lines.

Ok sure. Does this matter to scripts? Is it documented in
Documentation/process/submitting-patches.rst? I've seen both types, one
line or many lines, so I'm happy to mandate a policy as long as it's
documented. Maybe also checkpatch can complain about this so that people
don't submit patches "the wrong way".