dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
	daniel@ffwll.ch, airlied@linux.ie,
	maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	lyude@redhat.com
Cc: Thomas Zimmermann <tzimmermann@suse.de>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/8] drm: Put related statements next to each other in Makefile
Date: Wed, 30 Mar 2022 11:13:33 +0300	[thread overview]
Message-ID: <87ilrvdfiq.fsf@intel.com> (raw)
In-Reply-To: <20220322192743.14414-2-tzimmermann@suse.de>

On Tue, 22 Mar 2022, Thomas Zimmermann <tzimmermann@suse.de> wrote:
> Give the Makefile a bit more structure by putting rules for core,
> helpers, drivers, etc next to each other.

If you're up for it, I think it would be time to split these one per
line, in alphabetical order, to make the diffs nicer:

drm-y := \
	drm_aperture.o \
	drm_auth.o \
	...

Sure it takes up a lot of vertical screen estate, but IMO makes life
easier in the long run.

Definitely can be a follow-up, I don't really want to make the series
harder to land than it already is.


BR,
Jani.


>
> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
> ---
>  drivers/gpu/drm/Makefile | 23 +++++++++++++++++------
>  1 file changed, 17 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/Makefile b/drivers/gpu/drm/Makefile
> index c2ef5f9fce54..e5929437e13c 100644
> --- a/drivers/gpu/drm/Makefile
> +++ b/drivers/gpu/drm/Makefile
> @@ -18,7 +18,6 @@ drm-y       :=	drm_aperture.o drm_auth.o drm_cache.o \
>  		drm_syncobj.o drm_lease.o drm_writeback.o drm_client.o \
>  		drm_client_modeset.o drm_atomic_uapi.o \
>  		drm_managed.o drm_vblank_work.o
> -
>  drm-$(CONFIG_DRM_LEGACY) += drm_agpsupport.o drm_bufs.o drm_context.o drm_dma.o \
>  			    drm_hashtab.o drm_irq.o drm_legacy_misc.o drm_lock.o \
>  			    drm_memory.o drm_scatter.o drm_vm.o
> @@ -30,8 +29,16 @@ drm-$(CONFIG_PCI) += drm_pci.o
>  drm-$(CONFIG_DEBUG_FS) += drm_debugfs.o drm_debugfs_crc.o
>  drm-$(CONFIG_DRM_LOAD_EDID_FIRMWARE) += drm_edid_load.o
>  drm-$(CONFIG_DRM_PRIVACY_SCREEN) += drm_privacy_screen.o drm_privacy_screen_x86.o
> +obj-$(CONFIG_DRM)	+= drm.o
>  
>  obj-$(CONFIG_DRM_NOMODESET) += drm_nomodeset.o
> +obj-$(CONFIG_DRM_PANEL_ORIENTATION_QUIRKS) += drm_panel_orientation_quirks.o
> +
> +#
> +# Memory-management helpers
> +#
> +
> +obj-$(CONFIG_DRM_BUDDY) += drm_buddy.o
>  
>  drm_cma_helper-y := drm_gem_cma_helper.o
>  drm_cma_helper-$(CONFIG_DRM_KMS_HELPER) += drm_fb_cma_helper.o
> @@ -40,14 +47,16 @@ obj-$(CONFIG_DRM_GEM_CMA_HELPER) += drm_cma_helper.o
>  drm_shmem_helper-y := drm_gem_shmem_helper.o
>  obj-$(CONFIG_DRM_GEM_SHMEM_HELPER) += drm_shmem_helper.o
>  
> -obj-$(CONFIG_DRM_BUDDY) += drm_buddy.o
> -
>  drm_vram_helper-y := drm_gem_vram_helper.o
>  obj-$(CONFIG_DRM_VRAM_HELPER) += drm_vram_helper.o
>  
>  drm_ttm_helper-y := drm_gem_ttm_helper.o
>  obj-$(CONFIG_DRM_TTM_HELPER) += drm_ttm_helper.o
>  
> +#
> +# Modesetting helpers
> +#
> +
>  drm_kms_helper-y := drm_bridge_connector.o drm_crtc_helper.o \
>  		drm_dsc.o drm_encoder_slave.o drm_flip_work.o drm_hdcp.o \
>  		drm_probe_helper.o \
> @@ -60,14 +69,16 @@ drm_kms_helper-y := drm_bridge_connector.o drm_crtc_helper.o \
>  		drm_format_helper.o drm_self_refresh_helper.o drm_rect.o
>  drm_kms_helper-$(CONFIG_DRM_PANEL_BRIDGE) += bridge/panel.o
>  drm_kms_helper-$(CONFIG_DRM_FBDEV_EMULATION) += drm_fb_helper.o
> -
>  obj-$(CONFIG_DRM_KMS_HELPER) += drm_kms_helper.o
> +
> +#
> +# Drivers and the rest
> +#
> +
>  obj-$(CONFIG_DRM_DEBUG_SELFTEST) += selftests/
>  
> -obj-$(CONFIG_DRM)	+= drm.o
>  obj-$(CONFIG_DRM_MIPI_DBI) += drm_mipi_dbi.o
>  obj-$(CONFIG_DRM_MIPI_DSI) += drm_mipi_dsi.o
> -obj-$(CONFIG_DRM_PANEL_ORIENTATION_QUIRKS) += drm_panel_orientation_quirks.o
>  obj-y			+= arm/
>  obj-y			+= dp/
>  obj-$(CONFIG_DRM_TTM)	+= ttm/

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2022-03-30  8:13 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22 19:27 [PATCH 0/8] drm: Introduce display-helper library Thomas Zimmermann
2022-03-22 19:27 ` [PATCH 1/8] drm: Put related statements next to each other in Makefile Thomas Zimmermann
2022-03-30  8:13   ` Jani Nikula [this message]
2022-03-30  8:13   ` Javier Martinez Canillas
2022-03-22 19:27 ` [PATCH 2/8] drm: Rename dp/ to display/ Thomas Zimmermann
2022-03-30  9:04   ` Javier Martinez Canillas
2022-03-30  9:24     ` Thomas Zimmermann
2022-03-30 13:52   ` Alex Deucher
2022-03-22 19:27 ` [PATCH 3/8] drm/display: Introduce a DRM display-helper module Thomas Zimmermann
2022-03-30  9:23   ` Javier Martinez Canillas
2022-03-30 10:32     ` Thomas Zimmermann
2022-03-31  6:57       ` Javier Martinez Canillas
2022-04-06 19:08     ` Thomas Zimmermann
2022-04-07  7:43       ` Javier Martinez Canillas
2022-04-07  8:03         ` Thomas Zimmermann
2022-04-07  8:45           ` Jani Nikula
2022-04-18 18:13             ` Thomas Zimmermann
2022-03-22 19:27 ` [PATCH 4/8] drm/display: Split DisplayPort header into core and helper Thomas Zimmermann
2022-04-01  7:18   ` Javier Martinez Canillas
2022-03-22 19:27 ` [PATCH 5/8] drm/display: Move DSC header and helpers into display-helper module Thomas Zimmermann
2022-04-01  7:23   ` Javier Martinez Canillas
2022-03-22 19:27 ` [PATCH 6/8] drm/display: Move HDCP " Thomas Zimmermann
2022-03-30  7:12   ` Jani Nikula
2022-03-30  8:05     ` Thomas Zimmermann
2022-04-01  8:23   ` Javier Martinez Canillas
2022-03-22 19:27 ` [PATCH 7/8] drm/display: Move HDMI " Thomas Zimmermann
2022-03-30 10:35   ` Jani Nikula
2022-04-06 19:47     ` Thomas Zimmermann
2022-04-07  7:32       ` Jani Nikula
2022-04-07  7:34         ` Jani Nikula
2022-04-07  7:44           ` Thomas Zimmermann
2022-03-22 19:27 ` [PATCH 8/8] drm/display: Move SCDC helpers into display-helper library Thomas Zimmermann
2022-03-29 19:26 ` [PATCH 0/8] drm: Introduce " Lyude Paul

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=87ilrvdfiq.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=lyude@redhat.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=tzimmermann@suse.de \
    /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