linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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: Re: linux-next: Fixes tag needs some work in the rockchip tree
Date: Mon, 16 Jan 2023 11:19:14 +0100	[thread overview]
Message-ID: <1840312.tdWV9SEqCh@diego> (raw)
In-Reply-To: <20230116080947.2dcddeee@canb.auug.org.au>

Hi Stephen,

Am Sonntag, 15. Januar 2023, 22:09:47 CET schrieb Stephen Rothwell:
> 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")

thanks for noticing. I've checked this and amended the commit with the
correct id.

Thanks
Heiko



  reply	other threads:[~2023-01-16 10:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-15 21:09 linux-next: Fixes tag needs some work in the rockchip tree Stephen Rothwell
2023-01-16 10:19 ` Heiko Stübner [this message]
  -- 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=1840312.tdWV9SEqCh@diego \
    --to=heiko@sntech.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lucas.tanure@collabora.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;
as well as URLs for NNTP newsgroup(s).