linux-kernel - Re: [PATCH] efi_stub: update documentation on dtb= parameter

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] [day] [month] [year] [list]

Date:   Thu, 6 Sep 2018 17:52:06 +0000
From:   Grant Likely <Grant.Likely@....com>
To:     Jonathan Corbet <corbet@....net>
CC:     "linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "olof@...om.net" <olof@...om.net>,
        "scott.branden@...adcom.com" <scott.branden@...adcom.com>,
        Catalin Marinas <Catalin.Marinas@....com>,
        Will Deacon <Will.Deacon@....com>,
        "arnd@...db.de" <arnd@...db.de>,
        "leif.lindholm@...aro.org" <leif.lindholm@...aro.org>,
        "agraf@...e.de" <agraf@...e.de>,
        Ard Biesheuvel <ard.biesheuvel@...aro.org>, nd <nd@....com>
Subject: Re: [PATCH] efi_stub: update documentation on dtb= parameter



> On 6 Sep 2018, at 16:51, Jonathan Corbet <corbet@....net> wrote:
> 
> On Wed,  5 Sep 2018 20:07:50 +0100
> Grant Likely <grant.likely@....com> wrote:
> 
>> The dtb= parameter is no longer the primary mechanism for providing a
>> devicetree to the kernel. Now either firmware or the boot selector (ex.
>> Grub) should provide the devicetree and dtb= should only be used for
>> debug or when using firmware that doesn't understand DT.
>> Update the EFI stub documentation to reflect the current usage.
> 
> So I hate to be obnoxious, but...
> 
>> IMPORTANT NOTICE: The contents of this email and any attachments are
>> confidential and may also be privileged. If you are not the intended
>> recipient, please notify the sender immediately and do not disclose the
>> contents to any other person, use it for any purpose, or store or copy
>> the information in any medium. Thank you.
> 
> Can I get a version of the patch without this language?  Then I'll be glad
> to apply it.

Ugh. Well that was dumb. There is a magic trick I have to perform to get rid of the disclaimer, but it didn’t work this time. I’ll fix and get a new one out.

g.

> 
> Thanks,
> 
> jon