All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Diederik de Haas <didi.debian@cknow.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 rockchip tree
Date: Mon, 21 Oct 2024 23:13:13 +0200	[thread overview]
Message-ID: <22466915.EfDdHjke4D@diego> (raw)
In-Reply-To: <20241022080103.332d3024@canb.auug.org.au>

Hi,

Am Montag, 21. Oktober 2024, 23:01:03 CEST schrieb Stephen Rothwell:
> In commit
> 
>   273070dad96f ("arm64: dts: rockchip: Correct GPIO polarity on brcm BT nodes")
> 
> Fixes tag
> 
>   Fixes: a3a625086192 ("arm64: dts: rockchip: Fix reset-gpios property on brcm BT nodes")
> 
> has these problem(s):
> 
>   - Target SHA1 does not exist
> 
> Maybe you meant
> 
> Fixes: 2b6a3f857550 ("arm64: dts: rockchip: Fix reset-gpios property on brcm BT nodes")

thanks for noticing.

I've now double-checked the commit ids and amended the commit with the
correct id accordingly.

Heiko



  reply	other threads:[~2024-10-21 21:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21 21:01 linux-next: Fixes tag needs some work in the rockchip tree Stephen Rothwell
2024-10-21 21:13 ` 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-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
2023-01-15 21:09 Stephen Rothwell
2023-01-16 10:19 ` 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=22466915.EfDdHjke4D@diego \
    --to=heiko@sntech.de \
    --cc=didi.debian@cknow.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.