mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: airlied@linux.ie
Cc: linux-kernel@vger.kernel.org,
	DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: [git pull] VC4 fixes
Date: Wed, 18 Nov 2015 09:30:21 -0800	[thread overview]
Message-ID: <87a8qbgqqa.fsf@eliezer.anholt.net> (raw)

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

Hi Dave,

Here are a few little VC4 fixes for 4.4 that I didn't get in to you
before the -next pull request.  I dropped the feature-ish one I'd
mentioned, and also droppped the one I saw you included in the last
-fixes pull request.

The following changes since commit 8005c49d9aea74d382f474ce11afbbc7d7130bec:

  Linux 4.4-rc1 (2015-11-15 17:00:27 -0800)

are available in the git repository at:

  git@github.com:anholt/linux drm-vc4-fixes

for you to fetch changes up to bf893acc1675516fabf238a5ee3b52859c5687dc:

  drm/vc4: Make sure that planes aren't scaled. (2015-11-17 12:27:03 -0800)

----------------------------------------------------------------
Dan Carpenter (1):
      drm/vc4: checking for NULL instead of IS_ERR

Eric Anholt (2):
      drm/vc4: Fix some failure to track __iomem decorations on pointers.
      drm/vc4: Make sure that planes aren't scaled.

Julia Lawall (2):
      drm/vc4: fix platform_no_drv_owner.cocci warnings
      drm/vc4: fix itnull.cocci warnings

kbuild test robot (1):
      drm/vc4: vc4_plane_duplicate_state() can be static

 drivers/gpu/drm/vc4/vc4_crtc.c  |  9 +++++----
 drivers/gpu/drm/vc4/vc4_drv.c   |  1 -
 drivers/gpu/drm/vc4/vc4_hvs.c   |  8 ++++----
 drivers/gpu/drm/vc4/vc4_plane.c | 18 ++++++++++++++----
 4 files changed, 23 insertions(+), 13 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

                 reply	other threads:[~2015-11-18 17:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87a8qbgqqa.fsf@eliezer.anholt.net \
    --to=eric@anholt.net \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®