From: Jani Nikula <jani.nikula@intel.com>
To: "Kandpal, Suraj" <suraj.kandpal@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>,
"Deak, Imre" <imre.deak@intel.com>
Subject: RE: [PATCH 3/3] drm/i915: split out display register macros to a separate file
Date: Wed, 12 Feb 2025 11:41:17 +0200 [thread overview]
Message-ID: <87seojzeiq.fsf@intel.com> (raw)
In-Reply-To: <SN7PR11MB6750302257AFFFAB627C3A52E3FC2@SN7PR11MB6750.namprd11.prod.outlook.com>
On Wed, 12 Feb 2025, "Kandpal, Suraj" <suraj.kandpal@intel.com> wrote:
>> -----Original Message-----
>> From: Intel-xe <intel-xe-bounces@lists.freedesktop.org> On Behalf Of Jani
>> Nikula
>> Sent: Friday, February 7, 2025 7:05 PM
>> To: intel-gfx@lists.freedesktop.org; intel-xe@lists.freedesktop.org
>> Cc: Nikula, Jani <jani.nikula@intel.com>; ville.syrjala@linux.intel.com; Deak,
>> Imre <imre.deak@intel.com>
>> Subject: [PATCH 3/3] drm/i915: split out display register macros to a
>> separate file
>>
>> This is a scripted split of the display related register macros from
>> i915_reg.h to display/intel_display_regs.h. Basically move all the
>> macros that are only used in display code (or GVT). If there are users
>> in core i915 code or soc/, or no users anywhere, keep the macros in
>> i915_reg.h. This is done in groups of macros separated by blank lines,
>> moving the comments along with the groups.
>>
>> This is obviously a very crude approach. It's not perfect. But there are
>> 4.2k lines in i915_reg.h, and its refactoring has ground to a halt. This
>> is the big hammer that splits the file to two, and enables further
>> cleanup.
>>
>
> This is a really big patch and I may have very well missed something but
> Seeing that this is majorly code movement and things like conversion of 1<<x
> To reg_bit will need to happen In a different patch or series LGTM,
> Reviewed-by: Suraj Kandpal <suraj.kandpal@intel.com>
Oh, I sincerely hope you're aware of 'git show --color-moved'. Applying
the patch and looking at it with that makes it a breeze to review code
movement!
Thanks for the review.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-02-12 9:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 13:35 [PATCH 0/3] drm/i915: i915_reg.h display split Jani Nikula
2025-02-07 13:35 ` [PATCH 1/3] drm/i915/reg: use REG_BIT and friends to define DP registers Jani Nikula
2025-02-12 8:07 ` Kandpal, Suraj
2025-02-12 9:39 ` Jani Nikula
2025-02-12 12:42 ` Kandpal, Suraj
2025-02-07 13:35 ` [PATCH 2/3] drm/i915/reg: Remove some extra blank lines Jani Nikula
2025-02-12 8:07 ` Kandpal, Suraj
2025-02-07 13:35 ` [PATCH 3/3] drm/i915: split out display register macros to a separate file Jani Nikula
2025-02-12 8:48 ` Kandpal, Suraj
2025-02-12 9:41 ` Jani Nikula [this message]
2025-02-12 14:45 ` Ville Syrjälä
2025-02-12 15:12 ` Ville Syrjälä
2025-02-12 16:49 ` Jani Nikula
2025-02-07 16:12 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: i915_reg.h display split Patchwork
2025-02-07 19:54 ` ✗ i915.CI.BAT: 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=87seojzeiq.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=suraj.kandpal@intel.com \
--cc=ville.syrjala@linux.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