>-Original Message-
>From: AKASHI Takahiro
>Sent: Tuesday, October 29, 2019 10:49 AM
>To: Priyanka Jain ; Stefano Babic
>Cc: Tom Rini ; Udit Agarwal ;
>xypron.g...@gmx.de; ag...@csgraf.de; u-boot@lists.denx.de
>Subject: Re: [U-Boot] [RFC 06/15] secure boot: rena
t;Stefano Babic
> >Cc: xypron.g...@gmx.de; ag...@csgraf.de; u-boot@lists.denx.de
> >Subject: Re: [U-Boot] [RFC 06/15] secure boot: rename CONFIG_SECURE_BOOT
> >
> >On 19/09/19 17:02, Tom Rini wrote:
> >> On Wed, Sep 18, 2019 at 10:26:34AM +0900, AKASHI Takahiro w
>-Original Message-
>From: Stefano Babic
>Sent: Thursday, September 19, 2019 8:40 PM
>To: Tom Rini ; AKASHI Takahiro
>; Priyanka Jain ;
>Stefano Babic
>Cc: xypron.g...@gmx.de; ag...@csgraf.de; u-boot@lists.denx.de
>Subject: Re: [U-Boot] [RFC 06
On 19/09/19 17:02, Tom Rini wrote:
> On Wed, Sep 18, 2019 at 10:26:34AM +0900, AKASHI Takahiro wrote:
>
>> The configuration, CONFIG_SECURE_BOOT, was scattered among different
>> architecture directories for different implementation. This will prevent
>> UEFI secure boot from being added later.
On Wed, Sep 18, 2019 at 10:26:34AM +0900, AKASHI Takahiro wrote:
> The configuration, CONFIG_SECURE_BOOT, was scattered among different
> architecture directories for different implementation. This will prevent
> UEFI secure boot from being added later.
>
> So let's rename them, giving each
The configuration, CONFIG_SECURE_BOOT, was scattered among different
architecture directories for different implementation. This will prevent
UEFI secure boot from being added later.
So let's rename them, giving each implementation to different
configuration option. CONFIG_SECURE_BOOT still
6 matches
Mail list logo
