From: "Heiko Stübner" <heiko@sntech.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Lukasz Czechowski <lukasz.czechowski@thaumatec.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 rockchip tree
Date: Mon, 03 Feb 2025 10:21:50 +0100 [thread overview]
Message-ID: <3359983.44csPzL39Z@diego> (raw)
In-Reply-To: <20250203193313.0740304d@canb.auug.org.au>
Hi Stephen,
Am Montag, 3. Februar 2025, 09:33:13 MEZ schrieb Stephen Rothwell:
> Hi all,
>
> In commit
>
> 11534d3c53d5 ("arm64: dts: rockchip: Disable DMA for uart5 on px30-ringneck")
>
> Fixes tag
>
> Fixes: <commit hash>
thanks for noticing and should be fixed now.
It seems b4 smuggled that in from a _previous_ review iteration of the
series, where the fixes tag was suggested and explained:
✗ [PATCH v2 1/2] arm64: dts: rockchip: Move uart5 pin configuration to SoM dtsi
✗ [PATCH v2 2/2] arm64: dts: rockchip: Disable DMA for uart5 on px30-ringneck
+ Fixes: <commit hash> (✓ DKIM/cherry.de)
The commit of course already had a proper fixes tag.
next prev parent reply other threads:[~2025-02-03 9:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 8:33 linux-next: Fixes tag needs some work in the rockchip tree Stephen Rothwell
2025-02-03 9:21 ` Heiko Stübner [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-10 22:26 Stephen Rothwell
2025-07-11 11:39 ` Nicolas Frattaroli
2025-07-11 13:27 ` 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=3359983.44csPzL39Z@diego \
--to=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lukasz.czechowski@thaumatec.com \
--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