All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Murthy, Arun R" <arun.r.murthy@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 1/3] drm/i915: Use short PCH names consistently
Date: Thu, 30 Jun 2022 20:00:09 +0300	[thread overview]
Message-ID: <Yr3WmWe1K4OfLw+2@intel.com> (raw)
In-Reply-To: <DM6PR11MB31770ECA020E77AE853627C7BABA9@DM6PR11MB3177.namprd11.prod.outlook.com>

On Thu, Jun 30, 2022 at 03:50:15PM +0000, Murthy, Arun R wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > 
> > The comments regarding PCH compatibility use long vs.
> > short names inconsistently. Just use short names always.
> > 
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> >  drivers/gpu/drm/i915/intel_pch.c | 10 +++++-----
> >  1 file changed, 5 insertions(+), 5 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/intel_pch.c
> > b/drivers/gpu/drm/i915/intel_pch.c
> > index e2b2bbdc0714..94446cac6605 100644
> > --- a/drivers/gpu/drm/i915/intel_pch.c
> > +++ b/drivers/gpu/drm/i915/intel_pch.c
> > @@ -25,7 +25,7 @@ intel_pch_type(const struct drm_i915_private
> > *dev_priv, unsigned short id)
> >  		drm_dbg_kms(&dev_priv->drm, "Found PantherPoint
> > PCH\n");
> >  		drm_WARN_ON(&dev_priv->drm,
> >  			    GRAPHICS_VER(dev_priv) != 6 &&
> > !IS_IVYBRIDGE(dev_priv));
> > -		/* PantherPoint is CPT compatible */
> > +		/* PPT is CPT compatible */
> 
> 
> This is not the code but only comment, I feel elaborated names makes it more readable than abbreviation.

We rarely type out the full names for anything.

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2022-06-30 17:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30 15:05 [Intel-gfx] [PATCH 0/3] drm/i915: PCH type cleanup Ville Syrjala
2022-06-30 15:05 ` [Intel-gfx] [PATCH 1/3] drm/i915: Use short PCH names consistently Ville Syrjala
2022-06-30 15:50   ` Murthy, Arun R
2022-06-30 17:00     ` Ville Syrjälä [this message]
2022-07-01  9:53       ` Jani Nikula
2022-06-30 15:05 ` [Intel-gfx] [PATCH 2/3] drm/i915: Nuke PCH_MCC Ville Syrjala
2022-07-01  9:55   ` Jani Nikula
2022-07-01 12:21     ` Ville Syrjälä
2022-07-01 13:51       ` Jani Nikula
2022-06-30 15:06 ` [Intel-gfx] [PATCH 3/3] drm/i915: Nuke PCH_JSP Ville Syrjala
2022-06-30 15:55   ` Murthy, Arun R
2022-06-30 16:59     ` Ville Syrjälä
2022-07-01  9:57   ` Jani Nikula
2022-06-30 17:58 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: PCH type cleanup Patchwork
2022-06-30 18:19 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-07-01  9:47 ` [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=Yr3WmWe1K4OfLw+2@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=arun.r.murthy@intel.com \
    --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.