linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Ansuel Smith <ansuelsmth@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Boris Brezillon <boris.brezillon@collabora.com>,
	Miaoqian Lin <linmq006@gmail.com>,
	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 mtd-fixes tree
Date: Tue, 25 Jan 2022 10:33:51 +0100	[thread overview]
Message-ID: <20220125103351.2be25d78@xps13> (raw)
In-Reply-To: <61ee92ef.1c69fb81.95ef3.4aa6@mx.google.com>

Hello,

ansuelsmth@gmail.com wrote on Mon, 24 Jan 2022 12:52:12 +0100:

> On Mon, Jan 24, 2022 at 07:28:00AM +1100, Stephen Rothwell wrote:
> > Hi all,
> > 
> > In commit
> > 
> >   2b3d77cb5ce3 ("mtd: parsers: qcom: Fix kernel panic on skipped partition")
> > 
> > Fixes tag
> > 
> >   Fixes: 803eb12 ("mtd: parsers: Add Qcom SMEM parser")
> > 
> > has these problem(s):
> > 
> >   - SHA1 should be at least 12 digits long
> >     Can be fixed in the futrure 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").
> > 
> > In commit
> > 
> >   7815173a7ccb ("mtd: rawnand: ingenic: Fix missing put_device in ingenic_ecc_get")
> > 
> > Fixes tag
> > 
> >   Fixes: 15de8c6 ("mtd: rawnand: ingenic: Separate top-level and SoC specific code")
> > 
> > has these problem(s):
> > 
> >   - SHA1 should be at least 12 digits long
> >     Can be fixed in the futrure 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").
> > 
> > -- 
> > Cheers,
> > Stephen Rothwell  
> 
> Hi, sorry for the mistake. I wrongly copied the Fixes tag from a prev
> commit. Should I resend the series with the correct fixes?

Hey Stefan, thanks for the warnings.

Ansuel, Miaoquian, I've fixed the tags inline, don't forget to fix your
tooling for the next time ;)

Thanks,
Miquèl

      reply	other threads:[~2022-01-25  9:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-23 20:28 linux-next: Fixes tags need some work in the mtd-fixes tree Stephen Rothwell
2022-01-24 11:52 ` Ansuel Smith
2022-01-25  9:33   ` Miquel Raynal [this message]

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=20220125103351.2be25d78@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=ansuelsmth@gmail.com \
    --cc=boris.brezillon@collabora.com \
    --cc=linmq006@gmail.com \
    --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).