lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 26 Apr 2019 12:56:48 +1000
From:   Dave Airlie <airlied@...il.com>
To:     Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc:     Dave Airlie <airlied@...ux.ie>, Daniel Vetter <daniel@...ll.ch>,
        dri-devel <dri-devel@...ts.freedesktop.org>,
        nouveau <nouveau@...ts.freedesktop.org>,
        Sam Ravnborg <sam@...nborg.org>, zhoucm1 <David1.Zhou@....com>,
        amd-gfx mailing list <amd-gfx@...ts.freedesktop.org>,
        "James (Qian) Wang" <james.qian.wang@....com>,
        Ben Skeggs <bskeggs@...hat.com>,
        linux-arm-msm <linux-arm-msm@...r.kernel.org>,
        Intel Graphics Development <intel-gfx@...ts.freedesktop.org>,
        intel-gvt-dev@...ts.freedesktop.org,
        LKML <linux-kernel@...r.kernel.org>,
        "Koenig, Christian" <christian.koenig@....com>,
        "Deucher, Alexander" <alexander.deucher@....com>,
        freedreno@...ts.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2] drm: prefix header search paths with $(srctree)/

Daniel, drm-misc-next-fixes?

Dave.

On Fri, 26 Apr 2019 at 12:25, <yamada.masahiro@...ionext.com> wrote:
>
> Hi Dave,
>
> > -----Original Message-----
> > From: Dave Airlie [mailto:airlied@...il.com]
> > Sent: Friday, April 26, 2019 11:19 AM
> > To: Yamada, Masahiro/山田 真弘 <yamada.masahiro@...ionext.com>
> > Cc: David Airlie <airlied@...ux.ie>; Daniel Vetter <daniel@...ll.ch>;
> > dri-devel <dri-devel@...ts.freedesktop.org>; nouveau
> > <nouveau@...ts.freedesktop.org>; Sam Ravnborg <sam@...nborg.org>; David
> > (ChunMing) Zhou <David1.Zhou@....com>; amd-gfx mailing list
> > <amd-gfx@...ts.freedesktop.org>; James (Qian) Wang
> > <james.qian.wang@....com>; Ben Skeggs <bskeggs@...hat.com>;
> > linux-arm-msm <linux-arm-msm@...r.kernel.org>; Intel Graphics
> > Development <intel-gfx@...ts.freedesktop.org>;
> > intel-gvt-dev@...ts.freedesktop.org; Linux Kernel Mailing List
> > <linux-kernel@...r.kernel.org>; Christian König
> > <christian.koenig@....com>; Alex Deucher <alexander.deucher@....com>;
> > freedreno@...ts.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@...ionext.com> wrote:
> > >
> > > Hi.
> > >
> > >
> > > On Fri, Mar 29, 2019 at 8:37 PM Masahiro Yamada
> > > <yamada.masahiro@...ionext.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@...ionext.com>
> > > > Reviewed-by: Sam Ravnborg <sam@...nborg.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@...hat.com>
> > Dave.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ