From: Mike Snitzer <snitzer@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Alasdair G Kergon <agk@redhat.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Joe Thornber <ejt@redhat.com>
Subject: Re: linux-next: Fixes tag needs work in the device-mapper tree
Date: Tue, 15 Jan 2019 16:12:02 -0500 [thread overview]
Message-ID: <20190115211201.GA10746@redhat.com> (raw)
In-Reply-To: <20190116080251.17ba9771@canb.auug.org.au>
On Tue, Jan 15 2019 at 4:02pm -0500,
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> [I am experimenting with checking the Fixes tags in commits in linux-next.
> Please let me know if you think I am being too strict.]
>
> Hi all,
>
> Commit
>
> fc4d02aa0331 ("dm thin: fix passdown_double_checking_shared_status()")
>
> has a malformed Fixes tag:
>
> Fixes: 00a0ea33b49 ("dm thin: do not queue freed thin mapping for next stage processing")
>
> It should show at least 12 digits of the SHA1.
Fixed, thanks.
Mike
prev parent reply other threads:[~2019-01-15 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 21:02 linux-next: Fixes tag needs work in the device-mapper tree Stephen Rothwell
2019-01-15 21:12 ` Mike Snitzer [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=20190115211201.GA10746@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=ejt@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paul.gortmaker@windriver.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.