All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Katsuhiro Suzuki <katsuhiro@katsuster.net>
Subject: Re: linux-next: Fixes tag needs some work in the rockchip tree
Date: Tue, 23 Apr 2019 23:32:26 +0200	[thread overview]
Message-ID: <1748269.eM8PPa3JB8@phil> (raw)
In-Reply-To: <20190424072539.51aa27e2@canb.auug.org.au>

Am Dienstag, 23. April 2019, 23:25:39 CEST schrieb Stephen Rothwell:
> Hi Heiko,
> 
> In commit
> 
>   89c1f66ae88a ("arm64: dts: rockchip: fix IO domain voltage setting of APIO5 on rockpro64")
> 
> Fixes tag
> 
>   Fixes: e4f3fb4909 ("arm64: dts: rockchip: add initial dts support for Rockpro64")
> 
> has these problem(s):
> 
>   - SHA1 should be at least 12 digits long
>     Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
>     or later) just making sure it is not set (or set to "auto").

Thanks for that catch. I've amended the commit to have a correct
fixes commit-id.


Thanks
Heiko

  reply	other threads:[~2019-04-23 21:32 UTC|newest]

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

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=1748269.eM8PPa3JB8@phil \
    --to=heiko@sntech.de \
    --cc=katsuhiro@katsuster.net \
    --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.