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:   Fri, 18 Jan 2019 10:49:32 -0200
From:   Fabio Estevam <festevam@...il.com>
To:     Michael Ellerman <mpe@...erman.id.au>
Cc:     Stephen Boyd <sboyd@...nel.org>,
        Mike Turquette <mturquette@...libre.com>,
        Stephen Boyd <sboyd@...eaurora.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        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

Hi Michael,

On Fri, Jan 18, 2019 at 10:41 AM Michael Ellerman <mpe@...erman.id.au> wrote:

> Yeah "one line summary" is referring to the subject of the commit.
>
> So it doesn't explicitly say not to split it across lines, it probably
> should.
>
> eg: ?
>
> diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
> index 30dc00a364e8..12a283ba3929 100644
> --- a/Documentation/process/submitting-patches.rst
> +++ b/Documentation/process/submitting-patches.rst
> @@ -186,6 +186,8 @@ If your patch fixes a bug in a specific commit, e.g. you found an issue using
>
>         Fixes: e21d2170f366 ("video: remove unnecessary platform_set_drvdata()")
>
> +To ease parsing of the 'Fixes:' tag please don't split it across multiple lines.
> +
>  The following ``git config`` settings can be used to add a pretty format for
>  outputting the above style in the ``git log`` or ``git show`` commands::

Yes, I think this make it clearer. Thanks