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]
Message-ID: <AM0PR04MB4994403A3270455721C446D994A00@AM0PR04MB4994.eurprd04.prod.outlook.com>
Date:   Thu, 13 Dec 2018 09:18:28 +0000
From:   Ioana Ciocoi Radulescu <ruxandra.radulescu@....com>
To:     Olof Johansson <olof@...om.net>,
        Horia Geanta <horia.geanta@....com>
CC:     Marc Gonzalez <marc.w.gonzalez@...e.fr>, arm-soc <arm@...nel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v3 7/9] arm64: defconfig: Enable FSL_MC_BUS and
 FSL_MC_DPIO

> -----Original Message-----
> From: linux-kernel-owner@...r.kernel.org <linux-kernel-
> owner@...r.kernel.org> On Behalf Of Olof Johansson
> Sent: Thursday, December 13, 2018 8:48 AM
> To: Horia Geanta <horia.geanta@....com>
> Cc: Marc Gonzalez <marc.w.gonzalez@...e.fr>; arm-soc <arm@...nel.org>;
> Linux ARM <linux-arm-kernel@...ts.infradead.org>; LKML <linux-
> kernel@...r.kernel.org>
> Subject: Re: [PATCH v3 7/9] arm64: defconfig: Enable FSL_MC_BUS and
> FSL_MC_DPIO
> 
> On Fri, Nov 09, 2018 at 06:05:24AM +0000, Horia Geanta wrote:
> > On 11/9/2018 3:11 AM, Marc Gonzalez wrote:
> > > Commit e8342cc7954e ("enable CAAM crypto engine on QorIQ DPAA2
> SoCs")
> > > enabled CRYPTO_DEV_FSL_DPAA2_CAAM, which depends on
> FSL_MC_DPIO,
> > > which is not set. Enable FSL_MC_BUS, and build FSL_MC_DPIO and
> > > CRYPTO_DEV_FSL_DPAA2_CAAM as modules.
> > >
> > > Signed-off-by: Marc Gonzalez <marc.w.gonzalez@...e.fr>
> > Reviewed-by: Horia Geantă <horia.geanta@....com>
> 
> I had to redo this one, and when I did I noticed that there's also an ethernet
> driver. Should that be enabled as well?

Yes, it would be best to have the ethernet driver enabled too.

Thanks,
Ioana

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ