From: "Christian König" <deathsimple@vodafone.de>
To: Daniel Vetter <daniel@ffwll.ch>,
Jani Nikula <jani.nikula@intel.com>,
Ben Skeggs <bskeggs@redhat.com>,
"alexander.deucher@amd.com" <alexander.deucher@amd.com>,
Dave Airlie <airlied@gmail.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 0/7] drm & drivers: kill drm_get_connector_name() and drm_get_encoder_name()
Date: Mon, 26 May 2014 16:10:01 +0200 [thread overview]
Message-ID: <53834B39.9000905@vodafone.de> (raw)
In-Reply-To: <CAKMK7uF6dYEHyEovPKuNbKJasb3232-3x0Gz5=ZD05Yx7SSQuw@mail.gmail.com>
Am 26.05.2014 15:52, schrieb Daniel Vetter:
> On Mon, May 26, 2014 at 3:52 PM, Daniel Vetter <daniel@ffwll.ch> wrote:
>> On Mon, May 26, 2014 at 04:35:39PM +0300, Jani Nikula wrote:
>>> As requested by David [1],[2].
>>>
>>> These are on top of drm-intel-nightly which carries the required core
>>> patches adding ->name field to drm_connector and drm_encoder. The i915
>>> patches could go in right away, the last patch need to wait for radeon
>>> and nouveau patches to get merged, obviously.
>> For easier merging I'd might be best to throw them all into the
>> topic/core-stuff branch I have, since that's where your previous patch
>> also landed. I.e. I can't merge the i915 patches right away.
>>
>> Ben, Alex/Christian, Dave: Ack for this plan (and the patches)?
In general sounds like a good idea to me, no need for the wrappers when
they just retrieve a structure field.
Christian.
> Blergh, forgotten to put Dave onto the recipient list.
> -Daniel
>
>> -Daniel
>>
>>> BR,
>>> Jani.
>>>
>>>
>>> [1] http://mid.gmane.org/CANq1E4SBLr32kimS=Cxe5=sjZJJ9AVt7yxp3LfiOuMKSNC-CCA@mail.gmail.com
>>> [2] http://mid.gmane.org/CANq1E4QifeSoQ4pMfi1K+fgeCWYkvuBGDpjwand_Grabn+9Jow@mail.gmail.com
>>>
>>> Jani Nikula (7):
>>> drm/i915: replace drm_get_connector_name() with direct name field use
>>> drm/nouveau: replace drm_get_connector_name() with direct name field
>>> use
>>> drm/radeon: replace drm_get_connector_name() with direct name field
>>> use
>>> drm: replace drm_get_connector_name() with direct name field use
>>> drm/i915: replace drm_get_encoder_name() with direct name field use
>>> drm: replace drm_get_encoder_name() with direct name field use
>>> drm: drop drm_get_connector_name() and drm_get_encoder_name()
>>>
>>> drivers/gpu/drm/drm_crtc.c | 26 +++----------------------
>>> drivers/gpu/drm/drm_crtc_helper.c | 8 ++++----
>>> drivers/gpu/drm/drm_edid.c | 6 +++---
>>> drivers/gpu/drm/drm_edid_load.c | 2 +-
>>> drivers/gpu/drm/drm_fb_helper.c | 6 +++---
>>> drivers/gpu/drm/drm_probe_helper.c | 10 +++++-----
>>> drivers/gpu/drm/drm_sysfs.c | 6 +++---
>>> drivers/gpu/drm/i915/i915_debugfs.c | 6 +++---
>>> drivers/gpu/drm/i915/i915_irq.c | 8 ++++----
>>> drivers/gpu/drm/i915/intel_crt.c | 2 +-
>>> drivers/gpu/drm/i915/intel_display.c | 30 ++++++++++++++---------------
>>> drivers/gpu/drm/i915/intel_dp.c | 4 ++--
>>> drivers/gpu/drm/i915/intel_dvo.c | 2 +-
>>> drivers/gpu/drm/i915/intel_fbdev.c | 14 +++++++-------
>>> drivers/gpu/drm/i915/intel_hdmi.c | 2 +-
>>> drivers/gpu/drm/i915/intel_lvds.c | 2 +-
>>> drivers/gpu/drm/i915/intel_panel.c | 2 +-
>>> drivers/gpu/drm/i915/intel_sdvo.c | 8 ++++----
>>> drivers/gpu/drm/i915/intel_tv.c | 2 +-
>>> drivers/gpu/drm/nouveau/dispnv04/dac.c | 2 +-
>>> drivers/gpu/drm/nouveau/dispnv04/dfp.c | 2 +-
>>> drivers/gpu/drm/nouveau/dispnv04/disp.c | 2 +-
>>> drivers/gpu/drm/nouveau/dispnv04/tvnv04.c | 3 ++-
>>> drivers/gpu/drm/nouveau/dispnv04/tvnv17.c | 3 +--
>>> drivers/gpu/drm/nouveau/nouveau_connector.c | 8 ++++----
>>> drivers/gpu/drm/nouveau/nv50_display.c | 2 +-
>>> drivers/gpu/drm/radeon/radeon_connectors.c | 19 +++++++++++-------
>>> drivers/gpu/drm/radeon/radeon_display.c | 2 +-
>>> include/drm/drm_crtc.h | 2 --
>>> 29 files changed, 87 insertions(+), 104 deletions(-)
>>>
>>> --
>>> 1.9.1
>>>
>>> _______________________________________________
>>> dri-devel mailing list
>>> dri-devel@lists.freedesktop.org
>>> http://lists.freedesktop.org/mailman/listinfo/dri-devel
>> --
>> Daniel Vetter
>> Software Engineer, Intel Corporation
>> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
>
>
next prev parent reply other threads:[~2014-05-26 14:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 13:35 [PATCH 0/7] drm & drivers: kill drm_get_connector_name() and drm_get_encoder_name() Jani Nikula
2014-05-26 13:35 ` [PATCH 1/7] drm/i915: replace drm_get_connector_name() with direct name field use Jani Nikula
2014-05-26 13:35 ` [PATCH 2/7] drm/nouveau: " Jani Nikula
2014-05-26 15:50 ` Ilia Mirkin
2014-05-26 18:41 ` Jani Nikula
2014-05-26 13:35 ` [PATCH 3/7] drm/radeon: " Jani Nikula
2014-05-26 13:35 ` [PATCH 4/7] drm: " Jani Nikula
2014-05-26 13:35 ` [PATCH 5/7] drm/i915: replace drm_get_encoder_name() " Jani Nikula
2014-05-26 13:35 ` [PATCH 6/7] drm: " Jani Nikula
2014-05-26 13:35 ` [PATCH 7/7] drm: drop drm_get_connector_name() and drm_get_encoder_name() Jani Nikula
2014-05-26 13:52 ` [PATCH 0/7] drm & drivers: kill " Daniel Vetter
2014-05-26 13:52 ` Daniel Vetter
2014-05-26 14:10 ` Christian König [this message]
2014-05-27 15:35 ` Alex Deucher
2014-05-26 15:00 ` David Herrmann
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=53834B39.9000905@vodafone.de \
--to=deathsimple@vodafone.de \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=bskeggs@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.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.