From: Ansuel Smith <ansuelsmth@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Boris Brezillon <boris.brezillon@collabora.com>,
Miquel Raynal <miquel.raynal@bootlin.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: Mon, 24 Jan 2022 12:52:12 +0100 [thread overview]
Message-ID: <61ee92ef.1c69fb81.95ef3.4aa6@mx.google.com> (raw)
In-Reply-To: <20220124072800.14c492a5@canb.auug.org.au>
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?
--
Ansuel
next prev parent reply other threads:[~2022-01-24 11:52 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 [this message]
2022-01-25 9:33 ` Miquel Raynal
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=61ee92ef.1c69fb81.95ef3.4aa6@mx.google.com \
--to=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=miquel.raynal@bootlin.com \
--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.