[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <154775054438.169631.5111867106558251203@swboyd.mtv.corp.google.com>
Date: Thu, 17 Jan 2019 10:42:24 -0800
From: Stephen Boyd <sboyd@...nel.org>
To: Fabio Estevam <festevam@...il.com>
Cc: 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
Quoting Fabio Estevam (2019-01-16 17:25:21)
> On Wed, Jan 16, 2019 at 10:44 PM Stephen Boyd <sboyd@...nel.org> wrote:
>
> > Ok sure. Does this matter to scripts? Is it documented in
> > Documentation/process/submitting-patches.rst? I've seen both types, one
>
> From Documentation/process/submitting-patches.rst"
>
> "If your patch fixes a bug in a specific commit, e.g. you found an issue using
> ``git bisect``, please use the 'Fixes:' tag with the first 12 characters of
> the SHA-1 ID, and the one line summary. For example::
>
> Fixes: e21d2170f366 ("video: remove unnecessary platform_set_drvdata()")"
Yes but 'one line summary' is not clear to me. Does it mean the summary
line? Or the one line summary on one line regardless of commit message
column wrapping? Sorry to be pedantic but I can see how this can be
misunderstood.
Powered by blists - more mailing lists