From: Daniel Vetter <daniel@ffwll.ch>
To: Dave Airlie <airlied@gmail.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Dave Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
dri-devel <dri-devel@lists.freedesktop.org>,
nouveau <nouveau@lists.freedesktop.org>,
Sam Ravnborg <sam@ravnborg.org>, zhoucm1 <David1.Zhou@amd.com>,
amd-gfx mailing list <amd-gfx@lists.freedesktop.org>,
"James (Qian) Wang" <james.qian.wang@arm.com>,
Ben Skeggs <bskeggs@redhat.com>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
intel-gvt-dev@lists.freedesktop.org,
LKML <linux-kernel@vger.kernel.org>,
"Koenig, Christian" <christian.koenig@amd.com>,
"Deucher, Alexander" <alexander.deucher@amd.com>,
freedreno@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2] drm: prefix header search paths with $(srctree)/
Date: Fri, 26 Apr 2019 17:05:05 +0200 [thread overview]
Message-ID: <20190426150505.GA3271@phenom.ffwll.local> (raw)
In-Reply-To: <CAPM=9tyRHNp2R_No_0Gx0N59XR2RvD4=1G2GWgLLDxmKNk6JVg@mail.gmail.com>
On Fri, Apr 26, 2019 at 12:56:48PM +1000, Dave Airlie wrote:
> Daniel, drm-misc-next-fixes?
Makes sense. Pushed.
Cheers, Daniel
>
> Dave.
>
> On Fri, 26 Apr 2019 at 12:25, <yamada.masahiro@socionext.com> wrote:
> >
> > Hi Dave,
> >
> > > -----Original Message-----
> > > From: Dave Airlie [mailto:airlied@gmail.com]
> > > Sent: Friday, April 26, 2019 11:19 AM
> > > To: Yamada, Masahiro/山田 真弘 <yamada.masahiro@socionext.com>
> > > Cc: David Airlie <airlied@linux.ie>; Daniel Vetter <daniel@ffwll.ch>;
> > > dri-devel <dri-devel@lists.freedesktop.org>; nouveau
> > > <nouveau@lists.freedesktop.org>; Sam Ravnborg <sam@ravnborg.org>; David
> > > (ChunMing) Zhou <David1.Zhou@amd.com>; amd-gfx mailing list
> > > <amd-gfx@lists.freedesktop.org>; James (Qian) Wang
> > > <james.qian.wang@arm.com>; Ben Skeggs <bskeggs@redhat.com>;
> > > linux-arm-msm <linux-arm-msm@vger.kernel.org>; Intel Graphics
> > > Development <intel-gfx@lists.freedesktop.org>;
> > > intel-gvt-dev@lists.freedesktop.org; Linux Kernel Mailing List
> > > <linux-kernel@vger.kernel.org>; Christian König
> > > <christian.koenig@amd.com>; Alex Deucher <alexander.deucher@amd.com>;
> > > freedreno@lists.freedesktop.org
> > > Subject: Re: [Intel-gfx] [PATCH v2] drm: prefix header search paths with
> > > $(srctree)/
> > >
> > > On Fri, 26 Apr 2019 at 11:46, Masahiro Yamada
> > > <yamada.masahiro@socionext.com> wrote:
> > > >
> > > > Hi.
> > > >
> > > >
> > > > On Fri, Mar 29, 2019 at 8:37 PM Masahiro Yamada
> > > > <yamada.masahiro@socionext.com> wrote:
> > > > >
> > > > > Currently, the Kbuild core manipulates header search paths in a crazy
> > > > > way [1].
> > > > >
> > > > > To fix this mess, I want all Makefiles to add explicit $(srctree)/ to
> > > > > the search paths in the srctree. Some Makefiles are already written
> > > in
> > > > > that way, but not all. The goal of this work is to make the notation
> > > > > consistent, and finally get rid of the gross hacks.
> > > > >
> > > > > Having whitespaces after -I does not matter since commit 48f6e3cf5bc6
> > > > > ("kbuild: do not drop -I without parameter").
> > > > >
> > > > > [1]: https://patchwork.kernel.org/patch/9632347/
> > > > >
> > > > > Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> > > > > Reviewed-by: Sam Ravnborg <sam@ravnborg.org>
> > > > > ---
> > > > >
> > > > > I put all gpu/drm changes into a single patch because
> > > > > they are trivial conversion.
> > > > >
> > > > > If you are interested in the big picture of this work,
> > > > > the full patch set is available at the following URL.
> > > > >
> > > > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.g
> > > it build-test
> > > >
> > > >
> > > > Is somebody taking care of this?
> > > >
> > >
> > > Are you expecting this to be merged in the drm tree? if so please
> > > indicate that when posting.
> >
> >
> > Sorry for unclearness.
> >
> > Could you apply this to your drm tree?
> >
> > Thanks.
> >
> >
> >
> >
> > > I'd assumed this would go via kbuild tree.
> > >
> > > If the later,
> > > Acked-by: Dave Airlie <airlied@redhat.com>
> > > Dave.
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2019-04-26 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 11:32 [PATCH v2] drm: prefix header search paths with $(srctree)/ Masahiro Yamada
2019-03-29 12:01 ` james qian wang (Arm Technology China)
2019-03-29 14:24 ` Liviu Dudau
2019-04-26 1:36 ` Masahiro Yamada
2019-04-26 2:18 ` [Intel-gfx] " Dave Airlie
2019-04-26 2:25 ` yamada.masahiro
2019-04-26 2:56 ` Dave Airlie
2019-04-26 15:05 ` Daniel Vetter [this message]
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=20190426150505.GA3271@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=David1.Zhou@amd.com \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bskeggs@redhat.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=james.qian.wang@arm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=sam@ravnborg.org \
--cc=yamada.masahiro@socionext.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