From: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
To: Heiko Stuebner <heiko@sntech.de>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: 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 rockchip tree
Date: Fri, 11 Jul 2025 13:39:20 +0200 [thread overview]
Message-ID: <3455912.mvXUDI8C0e@workhorse> (raw)
In-Reply-To: <20250711082614.69765ef3@canb.auug.org.au>
On Friday, 11 July 2025 00:26:14 Central European Summer Time Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> fc276de7b63e ("arm64: dts: rockchip: adjust dcin regulator on ROCK 4D")
>
> Fixes tag
>
> Fixes: tag because there is no functional change here. I don't think
>
> has these problem(s):
>
> - No SHA1 recognised
>
> It looks like that Fixes tag was incorrectly picked up by automation
> from the mail thread and should be removed.
>
>
In the future I'll be sure to never mention the tag by its name
followed by a colon even mid sentence ever again, since tooling is
apparently a little over-eager here.
Good stuff.
next prev parent reply other threads:[~2025-07-11 11:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 22:26 linux-next: Fixes tag needs some work in the rockchip tree Stephen Rothwell
2025-07-11 11:39 ` Nicolas Frattaroli [this message]
2025-07-11 13:27 ` Heiko Stübner
-- strict thread matches above, loose matches on Subject: below --
2025-02-03 8:33 Stephen Rothwell
2025-02-03 9:21 ` Heiko Stübner
2024-10-21 21:01 Stephen Rothwell
2024-10-21 21:13 ` Heiko Stübner
2024-09-30 13:36 Stephen Rothwell
2024-09-30 13:55 ` Heiko Stübner
2023-01-29 22:02 Stephen Rothwell
2023-01-29 22:43 ` Heiko Stübner
2023-01-15 21:09 Stephen Rothwell
2023-01-16 10:19 ` Heiko Stübner
2022-01-29 23:23 Stephen Rothwell
2022-01-30 9:04 ` Heiko Stübner
2019-10-03 21:56 Stephen Rothwell
2019-10-03 22:45 ` Heiko Stuebner
2019-04-23 21:25 Stephen Rothwell
2019-04-23 21:32 ` Heiko Stuebner
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=3455912.mvXUDI8C0e@workhorse \
--to=nicolas.frattaroli@collabora.com \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.