All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jens Axboe <axboe@kernel.dk>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Igor Konopko <igor.j.konopko@intel.com>
Subject: linux-next: Fixes tags need some work in the block tree
Date: Tue, 7 May 2019 06:43:41 +1000	[thread overview]
Message-ID: <20190507064341.7bbbe26c@canb.auug.org.au> (raw)

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

Hi all,

In commit

  486b5aac85f6 ("lightnvm: pblk: fix lock order in pblk_rb_tear_down_check")

Fixes tag

  Fixes: a4bd217 ("lightnvm: physical block device (pblk) target")

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").

In commit

  4ca885241950 ("lightnvm: pblk: fix race during put line")

Fixes tag

  Fixes: a4bd217 ("lightnvm: physical block device (pblk) target")

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").

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2019-05-06 20:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-06 20:43 Stephen Rothwell [this message]
2019-12-27 19:55 linux-next: Fixes tags need some work in the block tree Stephen Rothwell
2019-12-27 20:27 ` Florian Fainelli
2019-12-27 20:29   ` Jens Axboe
2019-12-27 20:39     ` Stephen Rothwell
2019-12-27 20:44       ` Jens Axboe
2019-12-27 21:51         ` Florian Fainelli

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=20190507064341.7bbbe26c@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=axboe@kernel.dk \
    --cc=igor.j.konopko@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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.