From: "Christian König" <deathsimple@vodafone.de>
To: Dave Airlie <airlied@gmail.com>
Cc: Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 1/2] drm/ttm: move fpfn and lpfn into each placement
Date: Wed, 27 Aug 2014 13:34:14 +0200 [thread overview]
Message-ID: <53FDC236.8070106@vodafone.de> (raw)
In-Reply-To: <CAPM=9tzJd3fv1Hk11F7JdYkYRk=PNJLQRkznyX+=fqHxssc6-w@mail.gmail.com>
Hi Dave,
Am 27.08.2014 um 06:21 schrieb Dave Airlie:
> On 26 August 2014 21:28, Christian König <deathsimple@vodafone.de> wrote:
>> Hi Dave,
>>
>> any preferences how I can push this change upstream?
>>
>> Since it affects a whole bunch of drivers it would be nice if I could get
>> more reviews and/or acks on it. And if we just push it to you through the
>> Radeon tree it will probably cause a bunch of merge conflicts.
> Can you send me a separate git tree base on drm-next and I'll pull it
> into drm-next directly.
Sounds good, branch is on FDO and formal pull request below.
> Though it would be nice to get some acks on it, it doesn't look like a
> major amount of damage could be caused and -next should pick it up.
Agree, the change is rather straight forward.
My most concern is that I somehow missed something that only driver
maintainers know about, but I can confirm that all changed drivers still
compile fine on my box.
If anybody has additional comments on the patch or wants to give an
rb/ab just send a mail, the patch is on the list for quite a while now.
Regards,
Christian.
The following changes since commit 484048db6b4890bc433aac7f5e32fdcf1b2b4786:
Merge branch 'drm-next-3.18' of
git://people.freedesktop.org/~agd5f/linux into drm-next (2014-08-26
09:05:14 +1000)
are available in the git repository at:
git://people.freedesktop.org/~deathsimple/linux ttm_pfn
for you to fetch changes up to f1217ed09f827e42a49ffa6a5aab672aa6f57a65:
drm/ttm: move fpfn and lpfn into each placement v2 (2014-08-27
13:16:04 +0200)
----------------------------------------------------------------
Christian König (1):
drm/ttm: move fpfn and lpfn into each placement v2
drivers/gpu/drm/ast/ast_drv.h | 2 +-
drivers/gpu/drm/ast/ast_ttm.c | 20 ++++++++------
drivers/gpu/drm/bochs/bochs.h | 2 +-
drivers/gpu/drm/bochs/bochs_mm.c | 20 +++++++++-----
drivers/gpu/drm/cirrus/cirrus_drv.h | 2 +-
drivers/gpu/drm/cirrus/cirrus_ttm.c | 17 +++++++-----
drivers/gpu/drm/mgag200/mgag200_drv.h | 2 +-
drivers/gpu/drm/mgag200/mgag200_ttm.c | 20 ++++++++------
drivers/gpu/drm/nouveau/nouveau_bo.c | 52
++++++++++++++++++++++++-----------
drivers/gpu/drm/nouveau/nouveau_bo.h | 4 +--
drivers/gpu/drm/nouveau/nouveau_ttm.c | 9 +++----
drivers/gpu/drm/qxl/qxl_drv.h | 2 +-
drivers/gpu/drm/qxl/qxl_object.c | 17 +++++++-----
drivers/gpu/drm/qxl/qxl_ttm.c | 8 +++---
drivers/gpu/drm/radeon/radeon.h | 2 +-
drivers/gpu/drm/radeon/radeon_object.c | 71
++++++++++++++++++++++++++++++------------------
drivers/gpu/drm/radeon/radeon_ttm.c | 25 +++++++++--------
drivers/gpu/drm/radeon/radeon_uvd.c | 8 ++++--
drivers/gpu/drm/ttm/ttm_bo.c | 93
+++++++++++++++++++++++++++------------------------------------
drivers/gpu/drm/ttm/ttm_bo_manager.c | 9 +++----
drivers/gpu/drm/vmwgfx/vmwgfx_buffer.c | 136
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++-----------------------------------
drivers/gpu/drm/vmwgfx/vmwgfx_dmabuf.c | 22 ++++++++++-----
drivers/gpu/drm/vmwgfx/vmwgfx_fb.c | 10 +++++--
drivers/gpu/drm/vmwgfx/vmwgfx_gmrid_manager.c | 3 +--
include/drm/ttm/ttm_bo_api.h | 40
+++++++++++++--------------
include/drm/ttm/ttm_bo_driver.h | 3 +--
26 files changed, 346 insertions(+), 253 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-08-27 11:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 8:13 [PATCH 1/2] drm/ttm: move fpfn and lpfn into each placement Christian König
2014-08-22 8:13 ` [PATCH 2/2] drm/radeon: allow UVD to use a second 256MB segment Christian König
2014-08-25 15:51 ` [PATCH 1/2] drm/ttm: move fpfn and lpfn into each placement Alex Deucher
2014-08-26 11:28 ` Christian König
2014-08-27 4:21 ` Dave Airlie
2014-08-27 11:34 ` Christian König [this message]
2014-08-28 1:51 ` Michel Dänzer
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=53FDC236.8070106@vodafone.de \
--to=deathsimple@vodafone.de \
--cc=airlied@gmail.com \
--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.