From: AngeloGioacchino Del Regno <angelogioacchino.delregno@kernel•org>
To: Matthias Brugger <matthias.bgg@gmail•com>,
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 mediatek tree
Date: Thu, 13 Feb 2025 12:03:22 +0100 [thread overview]
Message-ID: <94700d2b-f796-4a8f-ad87-d75c8eaf1e62@kernel.org> (raw)
In-Reply-To: <9288348b-5792-4122-8705-76c00e463eae@gmail.com>
Il 13/02/25 09:56, Matthias Brugger ha scritto:
>
>
> On 12/02/2025 22:25, Stephen Rothwell wrote:
>> Hi all,
>>
>> In commit
>>
>> c4d75a56d161 ("arm64: dts: mediatek: mt8188: Assign apll1 clock as parent to
>> avoid hang")
>>
>> Fixes tag
>>
>> Fixes: 4dbec3a59a71 ("arm64: dts: mediatek: mt8188: Add audio support")
>>
>> has these problem(s):
>>
>> - Target SHA1 does not exist
>>
>> Maybe you meant
>>
>> Fixes: bd568ce198b8 ("arm64: dts: mediatek: mt8188: Add audio support")
>>
>
> Yes, that seems correct.
> Angelo will you update v6.14-next/dts64 ?
>
> Regards,
> Matthias
I have just fixed the issue and forcepushed both for-next and v6.14-next/dts64.
Many thanks! ...and sorry about the mistake.
Cheers,
Angelo
next prev parent reply other threads:[~2025-02-13 11:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 21:25 linux-next: Fixes tag needs some work in the mediatek tree Stephen Rothwell
2025-02-13 8:56 ` Matthias Brugger
2025-02-13 11:03 ` AngeloGioacchino Del Regno [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-02 22:15 Stephen Rothwell
2022-12-18 3:31 Stephen Rothwell
2022-11-08 21:15 Stephen Rothwell
2020-09-09 10:49 Stephen Rothwell
2020-09-09 13:56 ` Matthias Brugger
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=94700d2b-f796-4a8f-ad87-d75c8eaf1e62@kernel.org \
--to=angelogioacchino.delregno@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=matthias.bgg@gmail$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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