From: Konrad Dybcio <konrad.dybcio@somainline.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Andy Gross <agross@kernel.org>
Cc: Bjorn Andersson <bjorn.andersson@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: Thu, 14 Apr 2022 17:03:13 +0200 [thread overview]
Message-ID: <b20bc969-96e6-5368-e3f5-ba2748dae2a0@somainline.org> (raw)
In-Reply-To: <20220414074005.18cb9ed7@canb.auug.org.au>
On 13.04.2022 23:40, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 5827e2830467 ("arm64: dts: qcom: msm8994: Fix sleep clock name")
>
> Fixes tag
>
> Fixes: 9204da57cd65 ("arm64: dts: qcom: msm8994: Provide missing "xo_board" and "sleep_clk" to GCC")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: 4dd1ad619274 ("arm64: dts: qcom: msm8994: Provide missing "xo_board" and "sleep_clk" to GCC")
Yes, precisely this. Sorry for that, I probably forgot to rebase my local tree before checking that commit hash..
Bjorn, could you please fix that up directly in your tree?
Konrad
>
> Also, please keep all the commit message tags together at the end of
> the commit message.
>
next prev parent reply other threads:[~2022-04-14 15:45 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 21:40 Stephen Rothwell
2022-04-14 15:03 ` Konrad Dybcio [this message]
-- 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-05-29 21:49 Stephen Rothwell
2023-05-30 14:56 ` Bjorn Andersson
2023-05-31 13:25 ` Linus Walleij
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-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=b20bc969-96e6-5368-e3f5-ba2748dae2a0@somainline.org \
--to=konrad.dybcio@somainline.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®