From: Grant Likely <Grant.Likely@arm.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"olof@lixom.net" <olof@lixom.net>,
"scott.branden@broadcom.com" <scott.branden@broadcom.com>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Will Deacon <Will.Deacon@arm.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"leif.lindholm@linaro.org" <leif.lindholm@linaro.org>,
"agraf@suse.de" <agraf@suse.de>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>, nd <nd@arm.com>
Subject: Re: [PATCH] efi_stub: update documentation on dtb= parameter
Date: Thu, 6 Sep 2018 17:52:06 +0000 [thread overview]
Message-ID: <BFA61ADA-2AD9-4383-ADAA-9D660881865B@arm.com> (raw)
In-Reply-To: <20180906095111.1a74dfcd@lwn.net>
> On 6 Sep 2018, at 16:51, Jonathan Corbet <corbet@lwn.net> wrote:
>
> On Wed, 5 Sep 2018 20:07:50 +0100
> Grant Likely <grant.likely@arm.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
prev parent reply other threads:[~2018-09-06 17:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 19:07 Grant Likely
2018-09-05 19:30 ` Leif Lindholm
2018-09-05 19:39 ` Alexander Graf
2018-09-05 21:57 ` Olof Johansson
2018-09-06 15:51 ` Jonathan Corbet
2018-09-06 17:52 ` Grant Likely [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BFA61ADA-2AD9-4383-ADAA-9D660881865B@arm.com \
--to=grant.likely@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=Will.Deacon@arm.com \
--cc=agraf@suse.de \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=leif.lindholm@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nd@arm.com \
--cc=olof@lixom.net \
--cc=scott.branden@broadcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®