All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@gmail.com>
To: dri-devel <dri-devel@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: [git pull] drm legacy cleanups
Date: Wed, 24 Apr 2019 17:08:22 +1000	[thread overview]
Message-ID: <CAPM=9tztr1GoR0gr1CXPv8FsAXE4iuoRZDWKYovtnb6oDGF-Lg@mail.gmail.com> (raw)

Hi Daniel,

All these are r-b and been looked over, I think they are good to put
in next now. I haven't included the pci one I'll do that later.

Dave.

The following changes since commit dbb92471674a48892f5e50779425e03388073ab9:

  Revert "drm: allow render capable master with DRM_AUTH ioctls"
(2019-04-18 06:46:33 +1000)

are available in the Git repository at:

  git://people.freedesktop.org/~airlied/linux drm-legacy-cleanup

for you to fetch changes up to ee22f76306a68359c33809f8895eff603e71584b:

  drm/legacy: remove some legacy lock struct members (2019-04-24 12:36:32 +1000)

----------------------------------------------------------------
Dave Airlie (12):
      drm/nouveau: add kconfig option to turn off nouveau legacy contexts. (v3)
      drm/legacy: move drm_legacy_master_rmmaps to non-driver legacy header.
      drm/legacy: move map cleanups into drm_bufs.c
      drm/radeon: drop unused ati pcigart include.
      drm/legacy: move lock cleanup for master into lock file (v2)
      drm/legacy: move map_hash create/destroy into inlines
      drm/legacy: move init/destroy of struct members into legacy file
      drm/legacy: move legacy dev reinit into legacy misc
      drm/legacy: don't include any of ati_pcigart in legacy. (v2)
      drm: allow removal of legacy codepaths (v4.1)
      drm/legacy: place all drm legacy members under DRM_LEGACY.
      drm/legacy: remove some legacy lock struct members

 drivers/gpu/drm/Kconfig               |  4 ++
 drivers/gpu/drm/Makefile              |  9 ++--
 drivers/gpu/drm/drm_auth.c            | 19 +-------
 drivers/gpu/drm/drm_bufs.c            |  8 ++++
 drivers/gpu/drm/drm_drv.c             | 21 +++------
 drivers/gpu/drm/drm_file.c            | 25 ----------
 drivers/gpu/drm/drm_internal.h        |  2 +
 drivers/gpu/drm/drm_ioc32.c           | 13 +++++-
 drivers/gpu/drm/drm_ioctl.c           | 55 ++++++++++++----------
 drivers/gpu/drm/drm_irq.c             |  2 +
 drivers/gpu/drm/drm_legacy.h          | 87 ++++++++++++++++++++++++++++++++++-
 drivers/gpu/drm/drm_legacy_misc.c     | 82 +++++++++++++++++++++++++++++++++
 drivers/gpu/drm/drm_lock.c            | 19 ++++++++
 drivers/gpu/drm/drm_vm.c              |  2 +
 drivers/gpu/drm/nouveau/Kconfig       | 13 +++++-
 drivers/gpu/drm/nouveau/nouveau_drm.c |  7 ++-
 drivers/gpu/drm/radeon/radeon_drv.h   |  1 -
 include/drm/drm_auth.h                |  6 ++-
 include/drm/drm_device.h              |  3 +-
 include/drm/drm_file.h                |  2 +
 include/drm/drm_legacy.h              |  2 -
 21 files changed, 285 insertions(+), 97 deletions(-)
 create mode 100644 drivers/gpu/drm/drm_legacy_misc.c
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-04-24  7:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24  7:08 Dave Airlie [this message]
2019-04-24  8:39 ` [git pull] drm legacy cleanups 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='CAPM=9tztr1GoR0gr1CXPv8FsAXE4iuoRZDWKYovtnb6oDGF-Lg@mail.gmail.com' \
    --to=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.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 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.