public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
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>,
	Frank Wunderlich <frank-w@public-files.de>
Subject: Re: linux-next: Fixes tag needs some work in the mediatek tree
Date: Wed, 9 Sep 2020 15:56:56 +0200	[thread overview]
Message-ID: <cefa0d86-d9ed-d2be-91db-b060aafd8b52@gmail.com> (raw)
In-Reply-To: <20200909204951.5d3196d0@canb.auug.org.au>



On 09/09/2020 12:49, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>    845d404207f1 ("arm: dts: mt7623: move display nodes to separate mt7623n.dtsi")
> 
> Fixes tag
> 
>    Fixes: 1f6ed224594 ("arm: dts: mt7623: add Mali-450 device node")
> 
> 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").
> 

Fixed now and pushed again. Thanks for noting.

Regards,
Matthias

  reply	other threads:[~2020-09-09 16:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09 10:49 linux-next: Fixes tag needs some work in the mediatek tree Stephen Rothwell
2020-09-09 13:56 ` Matthias Brugger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-08 21:15 Stephen Rothwell
2022-12-18  3:31 Stephen Rothwell
2023-04-02 22:15 Stephen Rothwell
2025-02-12 21:25 Stephen Rothwell
2025-02-13  8:56 ` Matthias Brugger
2025-02-13 11:03   ` AngeloGioacchino Del Regno

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=cefa0d86-d9ed-d2be-91db-b060aafd8b52@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=frank-w@public-files.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox