From: Rob Herring <robh@kernel.org>
To: Eric Anholt <eric@anholt.net>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
david.emett@broadcom.com, thomas.spurden@broadcom.com
Subject: Re: [PATCH 4/4] drm/v3d: Use the new shmem helpers to reduce driver boilerplate.
Date: Fri, 8 Mar 2019 11:38:00 -0600 [thread overview]
Message-ID: <CAL_JsqJZHmHaxi1iK8qPin3QD36J7Tzz7XJCU0TQCpdAhcuj3A@mail.gmail.com> (raw)
In-Reply-To: <20190308161716.2466-5-eric@anholt.net>
On Fri, Mar 8, 2019 at 10:17 AM Eric Anholt <eric@anholt.net> wrote:
>
> Depends on
> https://patchwork.freedesktop.org/patch/290754/?series=57669&rev=1 --
> Rob and I have been talking about adding some more help for the
> dma_map_sg() code in v3d_mmu.c (which panfrost has a similar version
> of), but this already seems like a good cleanup.
There's an updated version here with the helper[1].
Rob
[1] https://gitlab.freedesktop.org/robh/linux-panfrost/commit/403e85012e9ee0a2a113bec757f545df193cfb7a
prev parent reply other threads:[~2019-03-08 17:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 16:17 [PATCH 0/4] drm/v3d: Add drm core helper, use shmem helpers Eric Anholt
2019-03-08 16:17 ` [PATCH 1/4] drm: Add helpers for locking an array of BO reservations Eric Anholt
2019-03-08 16:17 ` Eric Anholt
2019-03-08 17:33 ` Rob Herring
2019-03-08 17:46 ` Eric Anholt
2019-03-08 17:46 ` Eric Anholt
2019-03-12 17:37 ` Eric Anholt
2019-03-12 17:37 ` Eric Anholt
2019-03-12 19:50 ` Rob Herring
2019-03-14 16:28 ` Eric Anholt
2019-03-14 16:28 ` Eric Anholt
2019-03-08 16:17 ` [PATCH 2/4] drm/v3d: Use drm_gem_lock_reservations()/drm_gem_unlock_reservations() Eric Anholt
2019-03-08 16:17 ` [PATCH 3/4] drm/v3d: Remove some dead members of struct v3d_bo Eric Anholt
2019-03-08 16:17 ` Eric Anholt
2019-03-08 16:17 ` [PATCH 4/4] drm/v3d: Use the new shmem helpers to reduce driver boilerplate Eric Anholt
2019-03-08 16:17 ` Eric Anholt
2019-03-08 17:38 ` Rob Herring [this message]
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=CAL_JsqJZHmHaxi1iK8qPin3QD36J7Tzz7XJCU0TQCpdAhcuj3A@mail.gmail.com \
--to=robh@kernel.org \
--cc=david.emett@broadcom.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.spurden@broadcom.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 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.