From: Sven Peter <sven@svenpeter•dev>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Hector Martin <marcan@marcan•st>
Cc: Sven Peter <sven@kernel•org>,
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 asahi-soc tree
Date: Mon, 21 Jul 2025 19:50:02 +0200 [thread overview]
Message-ID: <80dff685-4bb2-4b10-b283-88573f0d9529@svenpeter.dev> (raw)
In-Reply-To: <20250721084007.341abfe2@canb.auug.org.au>
On 21.07.25 00:40, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> a622259af9eb ("arm64: dts: apple: Add bit offset to PMIC NVMEM node names")
>
> Fixes tag
>
> Fixes: 14b7178a76e2 ("arm64: dts: apple: Add PMIC NVMEM")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: d8bf82081c9e ("arm64: dts: apple: Add PMIC NVMEM")
>
Yup, that other SHA1 is a stale commit in a branch that never went
upstream in my local tree.
Thanks for catching it, should be fixed now.
Best,
Sven
prev parent reply other threads:[~2025-07-21 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-20 22:40 linux-next: Fixes tag needs some work in the asahi-soc tree Stephen Rothwell
2025-07-21 17:50 ` Sven Peter [this message]
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=80dff685-4bb2-4b10-b283-88573f0d9529@svenpeter.dev \
--to=sven@svenpeter$(echo .)dev \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=marcan@marcan$(echo .)st \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=sven@kernel$(echo .)org \
/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