public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Christoph Hellwig <hch@lst•de>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Ming Lei <ming.lei@redhat•com>
Subject: linux-next: Fixes tags need some work in the dma-mapping-fixes tree
Date: Wed, 23 Jan 2019 07:47:47 +1100	[thread overview]
Message-ID: <20190123074747.7cd44f12@canb.auug.org.au> (raw)

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

Hi Christoph,

In commit

  702e8ed37bed ("arm64/xen: fix xen-swiotlb cache flushing")

Fixes tag

  Fixes: 356da6d0cd ("dma-mapping: bypass indirect calls for dma-direct")

has these problem(s):

  - SHA1 should be at least 12 digits long

In commit

  8218a55b6b91 ("sbitmap: Protect swap_lock from hardirq")

Fixes tag

  Fixes: ab53dcfb3e7b ("sbitmap: Protect swap_lock from hardirq")

has these problem(s):

  - Target SHA1 does not exist

This later patch appears to already be in Linus' tree as commit
fe76fc6aaf53 (also with an incorrect Fixes tag :-()
-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2019-01-22 20:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-22 20:47 Stephen Rothwell [this message]
2019-01-23  7:19 ` linux-next: Fixes tags need some work in the dma-mapping-fixes tree Christoph Hellwig
2019-01-23 12:09   ` Stephen Rothwell
2019-01-23 12:13     ` Stephen Rothwell
2019-01-23 10:50 ` Thierry Reding

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=20190123074747.7cd44f12@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=hch@lst$(echo .)de \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=ming.lei@redhat$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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