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
| ||
|
Date: Wed, 16 Jan 2019 23:25:21 -0200 From: Fabio Estevam <festevam@...il.com> To: Stephen Boyd <sboyd@...nel.org> 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 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()")"
Powered by blists - more mailing lists