All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/5] display: prefer 3-letter acronym
Date: Thu, 19 Dec 2019 10:25:44 +0200	[thread overview]
Message-ID: <87lfr8yb5j.fsf@intel.com> (raw)
In-Reply-To: <20191219003654.rbcljj54pfkgs3h6@ldmartin-desk1.jf.intel.com>

On Wed, 18 Dec 2019, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Wed, Dec 18, 2019 at 04:27:30PM -0800, Lucas De Marchi wrote:
>>On Wed, Dec 18, 2019 at 08:07:55AM +0200, Jani Nikula wrote:
>>>On Tue, 17 Dec 2019, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
>>>>This bothered me for a while so I decided to give it a try: let's
>>>>normalize on using the platform acronym for function prefixes.
>>>
>>>The mixed use has always bothered me too.
>>>
>>>Acked-by: Jani Nikula <jani.nikula@intel.com>
>>>
>>>(Up next, IS_BROADWELL vs. IS_BDW_ULT etc... ;)
>>
>>actually next are the functions using <platform>_ prefix. I will leave
>>the IS_* macros for later or bundle them in the respective commits (not
>>that I didn't change IS_ICELAKE, IS_TIGERLAKE, etc.  Maybe it's a good
>>idea to just bundle them in next iteration.
>>
>
> also I was concentrating only on display/. If we are to change all the
> IS_* macros this has to be done in the entire driver.  Do you think it
> belongs in the same commit? It will be pretty intrusive.

Maybe just leave the IS_* later for now? Because it's going to be one
big ugly commit, or you have to add the TLA versions on the side and
migrate gradually. Either way it's pretty painful I think...

BR,
Jani.


>
> Lucas De Marchi
>
>>thanks
>>Lucas De Marchi
>>
>>
>>>
>>>
>>>>
>>>>This does the conversion for some platforms. There are others missing,
>>>>but I'm sending this early for the case the idea is shot down.
>>>>
>>>>Lucas De Marchi (5):
>>>>  drm/i915/display: prefer 3-letter acronym for haswell
>>>>  drm/i915/display: prefer 3-letter acronym for skylake
>>>>  drm/i915/display: prefer 3-letter acronym for cannonlake
>>>>  drm/i915/display: prefer 3-letter acronym for icelake
>>>>  drm/i915/display: prefer 3-letter acronym for ironlake
>>>>
>>>> drivers/gpu/drm/i915/display/intel_crt.c      |   6 +-
>>>> drivers/gpu/drm/i915/display/intel_ddi.c      |   4 +-
>>>> drivers/gpu/drm/i915/display/intel_display.c  | 278 +++++++++---------
>>>> drivers/gpu/drm/i915/display/intel_display.h  |   2 +-
>>>> drivers/gpu/drm/i915/display/intel_dp.c       |  34 +--
>>>> .../drm/i915/display/intel_fifo_underrun.c    |   6 +-
>>>> 6 files changed, 163 insertions(+), 167 deletions(-)
>>>
>>>-- 
>>>Jani Nikula, Intel Open Source Graphics Center

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-12-19  8:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-18  1:42 [Intel-gfx] [PATCH 0/5] display: prefer 3-letter acronym Lucas De Marchi
2019-12-18  1:42 ` [Intel-gfx] [PATCH 1/5] drm/i915/display: prefer 3-letter acronym for haswell Lucas De Marchi
2019-12-18  1:42 ` [Intel-gfx] [PATCH 2/5] drm/i915/display: prefer 3-letter acronym for skylake Lucas De Marchi
2019-12-18  1:42 ` [Intel-gfx] [PATCH 3/5] drm/i915/display: prefer 3-letter acronym for cannonlake Lucas De Marchi
2019-12-18  1:42 ` [Intel-gfx] [PATCH 4/5] drm/i915/display: prefer 3-letter acronym for icelake Lucas De Marchi
2019-12-18  1:42 ` [Intel-gfx] [PATCH 5/5] drm/i915/display: prefer 3-letter acronym for ironlake Lucas De Marchi
2019-12-18 12:59   ` Ville Syrjälä
2019-12-19  0:25     ` Lucas De Marchi
2019-12-18  3:10 ` [Intel-gfx] ✓ Fi.CI.BAT: success for display: prefer 3-letter acronym Patchwork
2019-12-18  6:07 ` [Intel-gfx] [PATCH 0/5] " Jani Nikula
2019-12-19  0:27   ` Lucas De Marchi
2019-12-19  0:36     ` Lucas De Marchi
2019-12-19  8:25       ` Jani Nikula [this message]
2019-12-18 19:37 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " 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=87lfr8yb5j.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@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.