Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Roper <matthew.d.roper@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org,
	Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/display: Include of display limits doesn't need 'display/'
Date: Wed, 7 Jun 2023 16:21:52 -0700	[thread overview]
Message-ID: <20230607232152.GW6953@mdroper-desk1.amr.corp.intel.com> (raw)
In-Reply-To: <878rcvteci.fsf@intel.com>

On Wed, Jun 07, 2023 at 07:41:01PM +0300, Jani Nikula wrote:
> On Wed, 07 Jun 2023, Matt Roper <matthew.d.roper@intel.com> wrote:
> > Drop the unnecessary directory prefix.  This also makes
> > intel_display_device.h easier to use from the Xe driver.
> >
> > Cc: Lucas De Marchi <lucas.demarchi@intel.com>
> > Cc: Jani Nikula <jani.nikula@linux.intel.com>
> > Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
> 
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>

Applied to drm-intel-next.  Thanks for the review.


Matt

> 
> > ---
> >  drivers/gpu/drm/i915/display/intel_display_device.h | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_display_device.h b/drivers/gpu/drm/i915/display/intel_display_device.h
> > index 4f931258d81d..706ff2aa1f55 100644
> > --- a/drivers/gpu/drm/i915/display/intel_display_device.h
> > +++ b/drivers/gpu/drm/i915/display/intel_display_device.h
> > @@ -8,7 +8,7 @@
> >  
> >  #include <linux/types.h>
> >  
> > -#include "display/intel_display_limits.h"
> > +#include "intel_display_limits.h"
> >  
> >  struct drm_i915_private;
> 
> -- 
> Jani Nikula, Intel Open Source Graphics Center

-- 
Matt Roper
Graphics Software Engineer
Linux GPU Platform Enablement
Intel Corporation

  reply	other threads:[~2023-06-07 23:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07 15:09 [Intel-gfx] [PATCH] drm/i915/display: Include of display limits doesn't need 'display/' Matt Roper
2023-06-07 16:41 ` Jani Nikula
2023-06-07 23:21   ` Matt Roper [this message]
2023-06-07 23:13 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2023-06-07 23:17 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-06-08 16:44 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=20230607232152.GW6953@mdroper-desk1.amr.corp.intel.com \
    --to=matthew.d.roper@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox