All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [RFC] drm: split build lists one per line and sort
Date: Tue, 11 Oct 2022 14:30:27 +0300	[thread overview]
Message-ID: <87bkqiy4vg.fsf@intel.com> (raw)
In-Reply-To: <Y0VEnTB950XYrhBI@ashyti-mobl2.lan>

On Tue, 11 Oct 2022, Andi Shyti <andi.shyti@linux.intel.com> wrote:
> Hi Jani,
>
>> While it takes more vertical space, sorted build lists with one object
>> per line are arguably easier to manage, especially when there are
>> conflicting changes.
>> 
>> Split anything with more than one object file.
>
> looks much better! Just an error below.
>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>>  drivers/gpu/drm/Makefile         | 106 ++++++++++++++++++++++---------
>>  drivers/gpu/drm/display/Makefile |  14 ++--
>>  2 files changed, 84 insertions(+), 36 deletions(-)
>> 
>> diff --git a/drivers/gpu/drm/Makefile b/drivers/gpu/drm/Makefile
>> index 25d0ba310509..c4e6ef321566 100644
>> --- a/drivers/gpu/drm/Makefile
>> +++ b/drivers/gpu/drm/Makefile
>> @@ -3,32 +3,70 @@
>>  # Makefile for the drm device driver.  This driver provides support for the
>>  # Direct Rendering Infrastructure (DRI) in XFree86 4.1.0 and higher.
>>  
>> -drm-y       :=	drm_aperture.o drm_auth.o drm_cache.o \
>> -		drm_file.o drm_gem.o drm_ioctl.o \
>> -		drm_drv.o \
>> -		drm_sysfs.o drm_mm.o \
>> -		drm_crtc.o drm_fourcc.o drm_modes.o drm_edid.o drm_displayid.o \
>> -		drm_trace_points.o drm_prime.o \
>> -		drm_vma_manager.o \
>> -		drm_modeset_lock.o drm_atomic.o drm_bridge.o \
>> -		drm_framebuffer.o drm_connector.o drm_blend.o \
>> -		drm_encoder.o drm_mode_object.o drm_property.o \
>> -		drm_plane.o drm_color_mgmt.o drm_print.o \
>> -		drm_dumb_buffers.o drm_mode_config.o drm_vblank.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
>> +drm-y := \
>> +	drm_aperture.o \
>> +	drm_atomic.o \
>> +	drm_atomic_uapi.o \
>> +	drm_auth.o drm_cache.o \
>
> You forgot to split here and drm_cache.o goes after drm_bridge.o
>
> Other than this there are no errors, I checked them all.

Good catch! I double checked before sending and missed this anyway.

> Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>

Thanks!

>
> Andi
>
>> +	drm_blend.o \
>> +	drm_bridge.o \
>> +	drm_client.o \
>> +	drm_client_modeset.o \
>> +	drm_color_mgmt.o \
>> +	drm_connector.o \
>> +	drm_crtc.o \
>
> [...]

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2022-10-11 11:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 10:01 [Intel-gfx] [RFC] drm: split build lists one per line and sort Jani Nikula
2022-10-11 10:01 ` Jani Nikula
2022-10-11 10:25 ` [Intel-gfx] " Andi Shyti
2022-10-11 11:30   ` Jani Nikula [this message]
2022-10-11 11:33 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-10-11 13:15 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork

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=87bkqiy4vg.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@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.