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  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Date:   Mon, 15 Apr 2019 17:43:10 +0200
From:   Daniel Vetter <daniel@...ll.ch>
To:     Joel Stanley <joel@....id.au>
Cc:     David Airlie <airlied@...ux.ie>, Andrew Jeffery <andrew@...id.au>,
        C├ędric Le Goater <clg@...d.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        dri-devel@...ts.freedesktop.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        kernel test robot <lkp@...el.com>,
        Daniel Vetter <daniel@...ll.ch>
Subject: Re: [PATCH v2] drm: aspeed: Clean up Kconfig options

On Mon, Apr 15, 2019 at 06:41:48PM +0800, Joel Stanley wrote:
> On Mon., 15 Apr. 2019, 17:32 Daniel Vetter, <daniel@...ll.ch> wrote:
> 
> > On Fri, Apr 05, 2019 at 06:41:17PM +1030, Joel Stanley wrote:
> > > The GFX IP is inside of the ASPEED BMC SoC so there is little use
> > > enabling it on a kernel that does not support ASPEED.
> > >
> > > When building with COMPILE_TEST the architecture many not have CMA
> > > support, so to avoid breaking the build we only select these options if
> > > the architecture supports the contiguous allocator.
> > >
> > > I suspect the DRM_PANEL came from a cut/paste error.
> > >
> > > Fixes: 4f2a8f5898ec ("drm: Add ASPEED GFX driver")
> > > Reported-by: Stephen Rothwell <sfr@...b.auug.org.au>
> > > Reported-by: kernel test robot <lkp@...el.com>
> > > Signed-off-by: Joel Stanley <joel@....id.au>
> >
> > Acked-by: Daniel Vetter <daniel.vetter@...ll.ch>
> >
> > Iirc you have commit rights, right?
> >
> 
> Can you please apply this one for me? I'm traveling and don't have my keys
> with me.

Ok, since it's holding up linux-next testing I've applied, in general it's
ok to just wait until you're back I think.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

Powered by blists - more mailing lists