From: khilman@baylibre•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM64: dts: meson-gx: make efuse read-only
Date: Mon, 19 Mar 2018 16:44:50 -0700 [thread overview]
Message-ID: <7h370vsk99.fsf@baylibre.com> (raw)
In-Reply-To: <20180316145021.8517-1-jbrunet@baylibre.com> (Jerome Brunet's message of "Fri, 16 Mar 2018 15:50:21 +0100")
Jerome Brunet <jbrunet@baylibre•com> writes:
> efuse is one time programmable, so it is safer to deny write request
> to this memory, unless the user is savvy enough to remove the read-only
> flag from DTB
>
> Signed-off-by: Jerome Brunet <jbrunet@baylibre•com>
Applied to v4.17/dt64,
Thanks,
Kevin
prev parent reply other threads:[~2018-03-19 23:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 14:50 [PATCH] ARM64: dts: meson-gx: make efuse read-only Jerome Brunet
2018-03-19 23:44 ` Kevin Hilman [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=7h370vsk99.fsf@baylibre.com \
--to=khilman@baylibre$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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