From: Bjorn Andersson <andersson@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andy Gross <agross@kernel.org>,
Linus Walleij <linus.walleij@linaro.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 qcom tree
Date: Tue, 30 May 2023 07:56:25 -0700 [thread overview]
Message-ID: <20230530145625.2znyjfd2bujfii5l@ripper> (raw)
In-Reply-To: <20230530074943.5b196424@canb.auug.org.au>
On Tue, May 30, 2023 at 07:49:43AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 8b9ca2f3ea45 ("ARM: dts: qcom-apq8060: Fix regulator node names")
>
> Fixes tag
>
> Fixes: 04715461abf7 ("ARM: dts: qcom-msm8660: align RPM regulators node name with bindings")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: 85055a1eecc1 ("ARM: dts: qcom-msm8660: align RPM regulators node name with bindings")
>
Thank you Stephen, the tag has now been corrected.
Regards,
Bjorn
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2023-05-30 14:52 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 21:49 linux-next: Fixes tag needs some work in the qcom tree Stephen Rothwell
2023-05-30 14:56 ` Bjorn Andersson [this message]
2023-05-31 13:25 ` Linus Walleij
-- strict thread matches above, loose matches on Subject: below --
2026-01-12 21:06 Stephen Rothwell
2026-01-12 23:00 ` Brian Masney
2026-01-16 19:42 ` Bjorn Andersson
2026-01-16 20:05 ` Brian Masney
2026-01-16 21:40 ` Bjorn Andersson
2024-07-08 8:13 Stephen Rothwell
2024-02-07 7:05 Stephen Rothwell
2023-07-23 22:53 Stephen Rothwell
2023-03-14 21:15 Stephen Rothwell
2023-03-13 21:37 Stephen Rothwell
2023-02-09 4:04 Stephen Rothwell
2023-02-09 10:02 ` Bartosz Golaszewski
2023-02-05 21:09 Stephen Rothwell
2023-01-19 6:04 Stephen Rothwell
2022-10-03 20:13 Stephen Rothwell
2022-09-14 7:23 Stephen Rothwell
2022-04-13 21:40 Stephen Rothwell
2022-04-14 15:03 ` Konrad Dybcio
2022-03-09 12:10 Stephen Rothwell
2022-02-13 10:39 Stephen Rothwell
2022-02-13 11:52 ` Robert Marko
2022-02-13 21:02 ` Stephen Rothwell
2022-02-14 4:53 ` Bjorn Andersson
2022-02-16 9:59 ` Robert Marko
2021-11-22 21:08 Stephen Rothwell
2021-09-20 22:24 Stephen Rothwell
2021-09-21 23:02 ` Stephen Rothwell
2021-09-21 23:31 ` Bjorn Andersson
2021-09-22 0:15 ` Stephen Rothwell
2021-07-20 7:25 Stephen Rothwell
2021-01-21 7:41 Stephen Rothwell
2021-01-21 8:50 ` Robert Foss
2020-02-12 7:18 Stephen Rothwell
2019-02-07 13:47 Stephen Rothwell
2019-02-07 17:06 ` Doug Anderson
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=20230530145625.2znyjfd2bujfii5l@ripper \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=linus.walleij@linaro.org \
--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.