public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Linus Walleij <linus.walleij@linaro•org>
Cc: Caleb Connolly <kc@postmarketos•org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: Fixes tags need some work in the pinctrl tree
Date: Fri, 22 Apr 2022 08:31:05 +1000	[thread overview]
Message-ID: <20220422083105.6b778b90@canb.auug.org.au> (raw)
In-Reply-To: <20220421091055.12d6465c@canb.auug.org.au>

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

Hi all,

On Thu, 21 Apr 2022 09:10:55 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> In commit
> 
>   6548c9dc711d ("pinctrl/rockchip: support deferring other gpio params")
> 
> Fixes tags
> 
>   Fixes: e7165b1d ("pinctrl/rockchip: add a queue for deferred pin output settings on probe")
>   Fixes: 59dd178e ("gpio/rockchip: fetch deferred output settings on probe")
> 
> have these problem(s):
> 
>   - SHA1 should be at least 12 digits long
>     This can be fixed for the future 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").

This is now commit aa696c2e8f33.

-- 
Cheers,
Stephen Rothwell

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

  reply	other threads:[~2022-04-21 22:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20 23:10 linux-next: Fixes tags need some work in the pinctrl tree Stephen Rothwell
2022-04-21 22:31 ` Stephen Rothwell [this message]
2022-04-22 20:57 ` Linus Walleij
2022-04-25 12:27   ` Caleb Connolly
2022-04-25 13:33     ` Linus Walleij
2022-04-25 13:35       ` Caleb Connolly

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=20220422083105.6b778b90@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=kc@postmarketos$(echo .)org \
    --cc=linus.walleij@linaro$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /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