From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mike Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dinh Nguyen <dinguyen@kernel.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: linux-next: Fixes tag needs some work in the clk tree
Date: Wed, 16 Jan 2019 08:34:40 +1100 [thread overview]
Message-ID: <20190116083440.11b6839c@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 445 bytes --]
[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.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-01-15 21:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 21:34 Stephen Rothwell [this message]
2019-01-16 22:35 ` linux-next: Fixes tag needs some work in the clk tree Stephen Boyd
2019-01-17 1:25 ` Fabio Estevam
2019-01-17 18:42 ` Stephen Boyd
2019-01-18 12:41 ` Michael Ellerman
2019-01-18 12:49 ` Fabio Estevam
2019-01-18 17:37 ` Stephen Boyd
2019-01-18 17:41 ` Nathan Chancellor
2019-01-18 18:36 ` Joe Perches
2019-05-26 10:35 Stephen Rothwell
2020-03-06 6:58 Stephen Rothwell
2020-09-23 11:46 Stephen Rothwell
2020-10-01 0:22 ` Stephen Boyd
2020-10-01 1:22 ` Stephen Rothwell
2020-12-07 22:05 Stephen Rothwell
2020-12-08 8:37 ` Geert Uytterhoeven
2020-12-09 17:29 ` Stephen Boyd
2020-12-10 7:52 ` Geert Uytterhoeven
2020-12-20 21:35 ` Stephen Rothwell
2020-12-21 8:07 ` Geert Uytterhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190116083440.11b6839c@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dinguyen@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=paul.gortmaker@windriver.com \
--cc=sboyd@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).