From: Abel Vesa <abel.vesa@nxp.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jacky Bai <ping.bai@nxp.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 clk-imx tree
Date: Fri, 1 Oct 2021 10:39:03 +0300 [thread overview]
Message-ID: <YVa7F+Y6BGUS9vXN@ryzen> (raw)
In-Reply-To: <20211001083304.3cab4195@canb.auug.org.au>
On 21-10-01 08:33:04, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> b00bad50a24f ("clk: imx: Fix the build break when clk-imx8ulp build as module")
>
> Fixes tag
>
> Fixes: 86ce2d393ff7 ("clk: imx: Add clock driver for imx8ulp")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: c43a801a5789 ("clk: imx: Add clock driver for imx8ulp")
>
Sorry about that. Fixed now.
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2021-10-01 7:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 22:33 linux-next: Fixes tag needs some work in the clk-imx tree Stephen Rothwell
2021-10-01 7:39 ` Abel Vesa [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-24 22:09 Stephen Rothwell
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=YVa7F+Y6BGUS9vXN@ryzen \
--to=abel.vesa@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ping.bai@nxp.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