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>,
	dan.carpenter@oracle.com
Subject: [GIT PULL] VC4 3D fixes for -next
Date: Mon, 21 Dec 2015 18:23:17 -0800	[thread overview]
Message-ID: <87poxzdxwq.fsf@eliezer.anholt.net> (raw)

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

I've decided to just send this fixes-for-next pull request now, even if
we don't have a patch for the CONFIG_PM_SLEEP build failure reviewed.
If you like my patch for that, I'd be happy to see it applied directly.

The following changes since commit 21de54b3c4d08d2b20e80876c6def0b421dfec2e:

  Merge tag 'drm-vc4-next-2015-12-11' of http://github.com/anholt/linux into drm-next (2015-12-15 10:43:27 +1000)

are available in the git repository at:

  http://github.com/anholt/linux tags/drm-vc4-next-2015-12-21

for you to fetch changes up to 5645e785cea2f33acdc5e5cee62b3ce8a00f1169:

  drm/vc4: fix an error code (2015-12-17 11:40:30 -0800)

----------------------------------------------------------------
This pull request brings in little fixes from Dan Carpenter for the 3D
support added in this -next cycle.

----------------------------------------------------------------
Dan Carpenter (3):
      drm/vc4: copy_to_user() returns the number of bytes remaining
      drm/vc4: allocate enough memory in vc4_save_hang_state()
      drm/vc4: fix an error code

 drivers/gpu/drm/vc4/vc4_gem.c | 41 ++++++++++++++++++++---------------------
 1 file changed, 20 insertions(+), 21 deletions(-)

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

                 reply	other threads:[~2015-12-22  2:23 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=87poxzdxwq.fsf@eliezer.anholt.net \
    --to=eric@anholt.net \
    --cc=airlied@linux.ie \
    --cc=dan.carpenter@oracle.com \
    --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®