From: Jani Nikula <jani.nikula@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Francois Dugast <francois.dugast@intel.com>,
intel-xe@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-xe] [PATCH 0/7] drm/xe: Code cleanup
Date: Tue, 08 Aug 2023 18:05:40 +0300 [thread overview]
Message-ID: <87v8dpshff.fsf@intel.com> (raw)
In-Reply-To: <a3bof7gwvoiqgcjlvhogomb45qhylrn6i3mbetvxofs4sthe5u@ka2lh4hbmsk6>
On Tue, 08 Aug 2023, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Tue, Aug 08, 2023 at 01:47:50PM +0300, Jani Nikula wrote:
>>On Mon, 17 Jul 2023, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
>>> On Thu, Jul 13, 2023 at 04:33:52PM -0400, Rodrigo Vivi wrote:
>>>>On Thu, Jul 13, 2023 at 03:06:04PM +0000, Francois Dugast wrote:
>>>>> Fix minor typos and reduce ERRORs reported by checkpatch.pl from 95 to 22.
>>>>
>>>>I wonder if we should do this with !fixup patches...
>>>
>>> I think that would be a nightmare to thread through the conflicts.
>>
>>For display it's a nightmare we have to plunge through. And this just
>>made it worse.
>
> This is automatically resolved when we move display up in the branch
> though. "Automatically" meaning that the pour sould doing the rebase
> has to resolve the conflicts. I don't like doing it, but what's the
> alternative? Last rebase I did a "squash-heavy approach" because moving
> display up means some commits don't make sense anymore, even if they
> apply correctly. Those coding style changes would just be squashed in
> the respective commits.
Squashing is easy if you have respective commits with 1:1 mapping, but
if you have one commit fixing multiple commits, it gets tricky.
BR,
Jani.
>
>
> Lucas De Marchi
>
>>
>>BR,
>>Jani.
>>
>>
>>> Let's just accept the mistakes happened when we werent' checking
>>> for checkpatch in CI.
>>>
>>> Lucas De Marchi
>>>
>>>>
>>>>But we anyway need this,
>>>>
>>>>Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>>>>for the series
>>>>
>>>>>
>>>>> Francois Dugast (7):
>>>>> drm/xe: Cleanup SPACING style issues
>>>>> drm/xe: Cleanup OPEN_BRACE style issues
>>>>> drm/xe: Cleanup POINTER_LOCATION style issues
>>>>> drm/xe: Cleanup CODE_INDENT style issues
>>>>> drm/xe: Cleanup TRAILING_WHITESPACE style issues
>>>>> drm/xe: Cleanup COMPLEX_MACRO style issues
>>>>> drm/xe: Fix typos
>>>>>
>>>>> drivers/gpu/drm/xe/compat-i915-headers/i915_drv.h | 4 ++--
>>>>> drivers/gpu/drm/xe/display/ext/intel_device_info.c | 11 ++++++++---
>>>>> drivers/gpu/drm/xe/display/xe_fb_pin.c | 4 ++--
>>>>> drivers/gpu/drm/xe/xe_device.h | 6 +++---
>>>>> drivers/gpu/drm/xe/xe_device_types.h | 4 ++--
>>>>> drivers/gpu/drm/xe/xe_engine.c | 4 ++--
>>>>> drivers/gpu/drm/xe/xe_force_wake.c | 2 +-
>>>>> drivers/gpu/drm/xe/xe_gt.h | 2 +-
>>>>> drivers/gpu/drm/xe/xe_gt_clock.c | 8 ++++----
>>>>> drivers/gpu/drm/xe/xe_gt_debugfs.c | 2 +-
>>>>> drivers/gpu/drm/xe/xe_gt_mcr.c | 3 ++-
>>>>> drivers/gpu/drm/xe/xe_gt_types.h | 8 ++++----
>>>>> drivers/gpu/drm/xe/xe_guc.c | 2 +-
>>>>> drivers/gpu/drm/xe/xe_guc_debugfs.c | 2 +-
>>>>> drivers/gpu/drm/xe/xe_guc_fwif.h | 12 ++++++------
>>>>> drivers/gpu/drm/xe/xe_guc_submit.c | 14 +++++++-------
>>>>> drivers/gpu/drm/xe/xe_huc_debugfs.c | 2 +-
>>>>> drivers/gpu/drm/xe/xe_hw_engine.c | 2 +-
>>>>> drivers/gpu/drm/xe/xe_lrc.c | 4 ++--
>>>>> drivers/gpu/drm/xe/xe_rtp.h | 4 ++--
>>>>> drivers/gpu/drm/xe/xe_rtp_helpers.h | 10 +++++-----
>>>>> drivers/gpu/drm/xe/xe_sched_job.c | 2 +-
>>>>> drivers/gpu/drm/xe/xe_uc.c | 10 +++++-----
>>>>> drivers/gpu/drm/xe/xe_uc_fw.c | 4 ++--
>>>>> drivers/gpu/drm/xe/xe_vm.c | 2 +-
>>>>> drivers/gpu/drm/xe/xe_wa.c | 4 ++--
>>>>> 26 files changed, 69 insertions(+), 63 deletions(-)
>>>>>
>>>>> --
>>>>> 2.34.1
>>>>>
>>
>>--
>>Jani Nikula, Intel Open Source Graphics Center
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-08-08 15:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 15:06 [Intel-xe] [PATCH 0/7] drm/xe: Code cleanup Francois Dugast
2023-07-13 15:06 ` [Intel-xe] [PATCH 1/7] drm/xe: Cleanup SPACING style issues Francois Dugast
2023-07-14 14:50 ` Matthew Brost
2023-07-13 15:06 ` [Intel-xe] [PATCH 2/7] drm/xe: Cleanup OPEN_BRACE " Francois Dugast
2023-07-14 14:10 ` Matthew Brost
2023-08-08 10:42 ` Jani Nikula
2023-07-13 15:06 ` [Intel-xe] [PATCH 3/7] drm/xe: Cleanup POINTER_LOCATION " Francois Dugast
2023-07-14 14:11 ` Matthew Brost
2023-07-13 15:06 ` [Intel-xe] [PATCH 4/7] drm/xe: Cleanup CODE_INDENT " Francois Dugast
2023-07-14 14:13 ` Matthew Brost
2023-07-13 15:06 ` [Intel-xe] [PATCH 5/7] drm/xe: Cleanup TRAILING_WHITESPACE " Francois Dugast
2023-07-14 14:22 ` Matthew Brost
2023-07-13 15:06 ` [Intel-xe] [PATCH 6/7] drm/xe: Cleanup COMPLEX_MACRO " Francois Dugast
2023-07-14 14:24 ` Matthew Brost
2023-07-13 15:06 ` [Intel-xe] [PATCH 7/7] drm/xe: Fix typos Francois Dugast
2023-07-14 14:23 ` Matthew Brost
2023-07-13 18:37 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Code cleanup Patchwork
2023-07-13 18:37 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-07-13 18:38 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-07-13 18:42 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-13 18:43 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-07-13 18:44 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-07-13 20:33 ` [Intel-xe] [PATCH 0/7] " Rodrigo Vivi
2023-07-17 3:47 ` Lucas De Marchi
2023-08-08 10:47 ` Jani Nikula
2023-08-08 14:37 ` Lucas De Marchi
2023-08-08 15:05 ` Jani Nikula [this message]
2023-08-08 23:39 ` Lucas De Marchi
2023-08-09 15:30 ` Jani Nikula
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=87v8dpshff.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=francois.dugast@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox