From: Jerome Brunet <jbrunet@baylibre.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Stephen Boyd <sboyd@kernel.org>
Cc: Mike Turquette <mturquette@baylibre.com>,
Chuan Liu <chuan.liu@amlogic.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the clk tree
Date: Fri, 08 Nov 2024 10:08:56 +0100 [thread overview]
Message-ID: <1jh68i2itz.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <20241108080914.65a7a03a@canb.auug.org.au> (Stephen Rothwell's message of "Fri, 8 Nov 2024 08:09:14 +1100")
On Fri 08 Nov 2024 at 08:09, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> In commit
>
> 5e052ef3c400 ("clk: meson: s4: pll: fix frac maximum value for hifi_pll")
>
> Fixes tag
>
> Fixes: 80344f4c1a1e ("clk: meson: s4: pll: hifi_pll support fractional multiplier")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: eb61a1264990 ("clk: meson: s4: pll: hifi_pll support fractional multiplier")
Indeed, I missed this. Thanks for pointing it out Stephen.
Stephen (Boyd), how do you want to handle this ? The commit will need
amending and it's something you've already pulled unfortunately. I'm
happy to redo amlogic clock update tag, if that's easier for you.
Stephen (Rothwell), I suppose (and hope) you are not checking all those
commit tags manually. Is there something available somewhere I should have
added to my routine checks for this type mistake ? A checkpatch.pl flag
I missed maybe ?
--
Jerome
next prev parent reply other threads:[~2024-11-08 9:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 21:09 linux-next: Fixes tag needs some work in the clk tree Stephen Rothwell
2024-11-08 9:08 ` Jerome Brunet [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2020-09-23 11:46 Stephen Rothwell
2020-10-01 0:22 ` Stephen Boyd
2020-10-01 1:22 ` Stephen Rothwell
2020-03-06 6:58 Stephen Rothwell
2019-05-26 10:35 Stephen Rothwell
2019-01-15 21:34 Stephen Rothwell
2019-01-16 22:35 ` 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
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=1jh68i2itz.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=chuan.liu@amlogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=sfr@canb.auug.org.au \
/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