public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Heiko Stuebner <heiko@sntech•de>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>,
	Lucas Tanure <lucas.tanure@collabora•com>
Subject: linux-next: Fixes tag needs some work in the rockchip tree
Date: Mon, 16 Jan 2023 08:09:47 +1100	[thread overview]
Message-ID: <20230116080947.2dcddeee@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 376 bytes --]

Hi all,

In commit

  0b86f9570e77 ("arm64: dts: rockchip: Fix RX delay for ethernet phy on rk3588s-rock5a")

Fixes tag

  Fixes: 55fa4c2a7a912 ("arm64: dts: rockchip: Add rock-5a board")

has these problem(s):

  - Target SHA1 does not exist

Maybe you meant

Fixes: d1824cf95799 ("arm64: dts: rockchip: Add rock-5a board")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2023-01-15 21:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-15 21:09 Stephen Rothwell [this message]
2023-01-16 10:19 ` linux-next: Fixes tag needs some work in the rockchip tree Heiko Stübner
  -- strict thread matches above, loose matches on Subject: below --
2025-07-10 22:26 Stephen Rothwell
2025-07-11 11:39 ` Nicolas Frattaroli
2025-07-11 13:27 ` Heiko Stübner
2025-02-03  8:33 Stephen Rothwell
2025-02-03  9:21 ` Heiko Stübner
2024-10-21 21:01 Stephen Rothwell
2024-10-21 21:13 ` Heiko Stübner
2024-09-30 13:36 Stephen Rothwell
2024-09-30 13:55 ` Heiko Stübner
2023-01-29 22:02 Stephen Rothwell
2023-01-29 22:43 ` Heiko Stübner
2022-01-29 23:23 Stephen Rothwell
2022-01-30  9:04 ` Heiko Stübner
2019-10-03 21:56 Stephen Rothwell
2019-10-03 22:45 ` Heiko Stuebner
2019-04-23 21:25 Stephen Rothwell
2019-04-23 21:32 ` Heiko Stuebner

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=20230116080947.2dcddeee@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=heiko@sntech$(echo .)de \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=lucas.tanure@collabora$(echo .)com \
    /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