linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.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>,
	Huang Pei <huangpei@loongson.cn>
Subject: Re: linux-next: Fixes tag needs some work in the mips-fixes tree
Date: Thu, 3 Sep 2020 12:01:19 +0200	[thread overview]
Message-ID: <20200903100118.GA9038@alpha.franken.de> (raw)
In-Reply-To: <20200903184259.74a4f24f@canb.auug.org.au>

On Thu, Sep 03, 2020 at 06:42:59PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   f8a005e1632c ("MIPS: add missing MSACSR and upper MSA initialization")
> 
> Fixes tag
> 
>   Fixes: cc97ab235f ("MIPS: Simplify FP context initialization")
> 
> 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").

it's fixed now.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2020-09-03 10:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03  8:42 linux-next: Fixes tag needs some work in the mips-fixes tree Stephen Rothwell
2020-09-03 10:01 ` Thomas Bogendoerfer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-02-26 20:17 Stephen Rothwell
2020-02-27 13:43 ` Paul Cercueil
2020-02-27 14:02   ` Thomas Bogendoerfer
2020-02-19 20:36 Stephen Rothwell

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=20200903100118.GA9038@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=huangpei@loongson.cn \
    --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;
as well as URLs for NNTP newsgroup(s).