From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: prefix header search path with $(srctree)/
Date: Thu, 27 Jun 2019 10:49:54 +0300 [thread overview]
Message-ID: <87k1d7qxgd.fsf@intel.com> (raw)
In-Reply-To: <156155988517.26855.8106595872151907631@skylake-alporthouse-com>
On Wed, 26 Jun 2019, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Jani Nikula (2019-06-26 15:36:17)
>> Per commit 43068cb7ba1f ("drm: prefix header search paths with
>> $(srctree)/") this is what we should be doing. Follow suit.
>
> Bleugh, it's not mentioned in Documention/kbuild but it is used in one
> of their examples.
>
>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> for some value of review.
Thanks, pushed both.
BR,
Jani.
> -Chris
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-06-27 7:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 14:36 [PATCH 1/2] drm/i915: prefix header search path with $(srctree)/ Jani Nikula
2019-06-26 14:36 ` [PATCH 2/2] drm/i915: add header search path to subdir Makefiles Jani Nikula
2019-06-26 14:39 ` Chris Wilson
2019-06-26 14:38 ` [PATCH 1/2] drm/i915: prefix header search path with $(srctree)/ Chris Wilson
2019-06-27 7:49 ` Jani Nikula [this message]
2019-06-26 14:52 ` ✗ Fi.CI.SPARSE: warning for series starting with [1/2] " Patchwork
2019-06-26 15:35 ` ✓ Fi.CI.BAT: success " Patchwork
2019-06-27 0:38 ` ✓ 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=87k1d7qxgd.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=chris@chris-wilson.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox