From: Christoph Hellwig <hch@lst.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christoph Hellwig <hch@lst.de>,
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: Re: linux-next: Fixes tags need some work in the dma-mapping-fixes tree
Date: Wed, 23 Jan 2019 08:19:33 +0100 [thread overview]
Message-ID: <20190123071933.GA24861@lst.de> (raw)
In-Reply-To: <20190123074747.7cd44f12@canb.auug.org.au>
On Wed, Jan 23, 2019 at 07:47:47AM +1100, Stephen Rothwell wrote:
> 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
When did we decide on that? As far as I know it was bumped to 10
a while ago. 12 basically makes the line even more unreadable.
> 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 :-()
That commit is not from the dma-mapping tree..
next prev parent reply other threads:[~2019-01-23 7:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 20:47 linux-next: Fixes tags need some work in the dma-mapping-fixes tree Stephen Rothwell
2019-01-23 7:19 ` Christoph Hellwig [this message]
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=20190123071933.GA24861@lst.de \
--to=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ming.lei@redhat.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.