linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Airlie <airlied@linux.ie>, DRI <dri-devel@lists.freedesktop.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Thomas Hellstrom <thellstrom@vmware.com>,
	Deepak Rawat <drawat@vmware.com>, Christoph Hellwig <hch@lst.de>
Subject: linux-next: Fixes tags need some work in the drm-fixes tree
Date: Thu, 7 Feb 2019 22:45:39 +1100	[thread overview]
Message-ID: <20190207224539.52b5e209@canb.auug.org.au> (raw)

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

Hi all,

In commit

  4cbfa1e6c09e ("drm/vmwgfx: Fix setting of dma masks")

Fixes tag

  Fixes: 0d00c488f3de: ("drm/vmwgfx: Fix the driver for large dma addresses")

has these problem(s):

  - ':' unexpected after SHA1

In commit

  479d59026fe4 ("drm/vmwgfx: Also check for crtc status while checking for DU active")

Fixes tag

  Fixes: 9da6e26c0aae: ("drm/vmwgfx: Fix a layout race condition")

has these problem(s):

  - ':' unexpected after SHA1

In commit

  51fdbeb4ca1a ("drm/vmwgfx: Fix an uninitialized fence handle value")

Fixes tag

  Fixes: 2724b2d54cda: ("drm/vmwgfx: Use new validation interface for the modesetting code v2")

has these problem(s):

  - ':' unexpected after SHA1

In commit

  728354c005c3 ("drm/vmwgfx: Return error code from vmw_execbuf_copy_fence_user")

Fixes tag

  Fixes: ae2a104058e2: ("vmwgfx: Implement fence objects")

has these problem(s):

  - ':' unexpected after SHA1

In commit

  2b3cd6249b14 ("drm/vmwgfx: fix the check when to use dma_alloc_coherent")

Fixes tags

  Fixes: 55897af630 ("dma-direct: merge swiotlb_dma_ops into the dma_direct code")
  Fixes: 356da6d0cd ("dma-mapping: bypass indirect calls for dma-direct")

have 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-02-07 11:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-07 11:45 Stephen Rothwell [this message]
2019-02-13 10:36 linux-next: Fixes tags need some work in the drm-fixes tree Stephen Rothwell
2019-06-21 11:41 Stephen Rothwell
2019-06-21 12:45 ` Philipp Zabel
2019-06-21 15:49   ` Daniel Vetter

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=20190207224539.52b5e209@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=airlied@linux.ie \
    --cc=drawat@vmware.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=thellstrom@vmware.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;
as well as URLs for NNTP newsgroup(s).