From: Arnd Bergmann <arnd@arndb.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
ARM <linux-arm-kernel@lists.infradead.org>,
Conor Dooley <conor.dooley@microchip.com>,
Conor Dooley <mail@conchuod.ie>,
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 arm-soc tree
Date: Mon, 28 Feb 2022 16:57:33 +0100 [thread overview]
Message-ID: <CAK8P3a0+fGJniopx1q5OhY9zk-PNemcUZ2XXx-JWOLGdDwmu5A@mail.gmail.com> (raw)
In-Reply-To: <20220301025101.7fb280fd@canb.auug.org.au>
On Mon, Feb 28, 2022 at 4:51 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> In commit
>
> ed40a635b5ec ("soc: microchip: make mpfs_sys_controller_put static")
>
> Fixes tag
>
> Fixes: dsafsdfd0054 ("soc: add microchip polarfire soc system controller")
>
> has these problem(s):
>
> - No SHA1 recognised
>
> Maybe you meant
>
> Fixes: d0054a470c33 ("soc: add microchip polarfire soc system controller")
Fixed, thanks!
next prev parent reply other threads:[~2022-02-28 16:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 15:51 linux-next: Fixes tag needs some work in the arm-soc tree Stephen Rothwell
2022-02-28 15:57 ` Arnd Bergmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-05 9:21 Stephen Rothwell
2020-01-12 19:56 Stephen Rothwell
2020-01-12 20:01 ` Olof Johansson
2019-11-14 9:21 Stephen Rothwell
2019-11-14 11:01 ` Sudeep Holla
2019-09-04 21:24 Stephen Rothwell
2019-08-15 21:43 Stephen Rothwell
2019-08-15 10:10 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=CAK8P3a0+fGJniopx1q5OhY9zk-PNemcUZ2XXx-JWOLGdDwmu5A@mail.gmail.com \
--to=arnd@arndb.de \
--cc=conor.dooley@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mail@conchuod.ie \
--cc=olof@lixom.net \
--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;
as well as URLs for NNTP newsgroup(s).