public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Boris Brezillon <boris.brezillon@collabora.com>
Cc: Ansuel Smith <ansuelsmth@gmail.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: linux-next: Fixes tags need some work in the mtd-fixes tree
Date: Mon, 24 Jan 2022 07:28:00 +1100	[thread overview]
Message-ID: <20220124072800.14c492a5@canb.auug.org.au> (raw)

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

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

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

             reply	other threads:[~2022-01-23 20:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-23 20:28 Stephen Rothwell [this message]
2022-01-24 11:52 ` linux-next: Fixes tags need some work in the mtd-fixes tree Ansuel Smith
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=20220124072800.14c492a5@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --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=miquel.raynal@bootlin.com \
    /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