From: Greg KH <greg@kroah.com>
To: Pantelis Antoniou <panto@antoniou-consulting.com>
Cc: Rob Herring <robherring2@gmail.com>,
Grant Likely <grant.likely@secretlab.ca>,
Andrew Morton <akpm@linux-foundation.org>,
Matt Porter <mporter@konsulko.com>,
Koen Kooi <koen@dominion.thruhere.net>,
Guenter Roeck <linux@roeck-us.net>,
devicetree@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-api@vger.kernel.org
Subject: Re: [PATCH v3 4/4] Documentation: ABI: /sys/firmware/devicetree/overlays
Date: Mon, 27 Apr 2015 20:11:38 +0200 [thread overview]
Message-ID: <20150427181138.GA27043@kroah.com> (raw)
In-Reply-To: <C49CC7F9-C877-4590-AA63-F45D2D8E8CDC@antoniou-consulting.com>
On Mon, Apr 27, 2015 at 08:51:20PM +0300, Pantelis Antoniou wrote:
> Hi Greg,
>
> > On Apr 24, 2015, at 23:31 , Greg KH <greg@kroah.com> wrote:
> >
> > On Fri, Apr 24, 2015 at 12:45:44PM +0300, Pantelis Antoniou wrote:
> >> Documentation ABI entry for overlays sysfs entries.
> >>
> >> Signed-off-by: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
> >> ---
> >> .../ABI/testing/sysfs-firmware-devicetree-overlays | 23 ++++++++++++++++++++++
> >> 1 file changed, 23 insertions(+)
> >> create mode 100644 Documentation/ABI/testing/sysfs-firmware-devicetree-overlays
> >>
> >> diff --git a/Documentation/ABI/testing/sysfs-firmware-devicetree-overlays b/Documentation/ABI/testing/sysfs-firmware-devicetree-overlays
> >> new file mode 100644
> >> index 0000000..6b81f1c
> >> --- /dev/null
> >> +++ b/Documentation/ABI/testing/sysfs-firmware-devicetree-overlays
> >> @@ -0,0 +1,23 @@
> >> +What: /sys/firmware/devicetree/overlays/
> >> +Date: March 2015
> >> +Contact: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
> >> +Description:
> >> + This directory contains the applied device tree overlays of
> >> + the running system, as directories of the overlay id.
> >
> > "as"?
> >
> >> +
> >> + enable: The master enable switch, by default is 1, and when
> >> + set to 0 it cannot be re-enabled for security reasons.
> >
> > What are those reasons?
> >
>
> There’s a whole subthread with Grant & Kees going over security concerns.
>
> http://comments.gmane.org/gmane.linux.drivers.devicetree/101871
Great, document it here please, so that others know this :)
thanks,
greg k-h
prev parent reply other threads:[~2015-04-27 18:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 9:45 [PATCH v3 0/4] of: overlay: kobject & sysfs'ation Pantelis Antoniou
2015-04-24 9:45 ` [PATCH v3 1/4] of: overlay: kobjectify overlay objects Pantelis Antoniou
2015-04-24 9:45 ` [PATCH v3 2/4] of: overlay: global sysfs enable attribute Pantelis Antoniou
2015-04-24 20:29 ` Greg KH
2015-04-27 18:13 ` Pantelis Antoniou
2015-04-27 18:39 ` Greg KH
2015-04-27 18:43 ` Pantelis Antoniou
2015-04-24 20:36 ` Greg KH
2015-04-27 18:25 ` Pantelis Antoniou
2015-04-24 9:45 ` [PATCH v3 3/4] of: overlay: add per overlay sysfs attributes Pantelis Antoniou
2015-04-24 9:45 ` [PATCH v3 4/4] Documentation: ABI: /sys/firmware/devicetree/overlays Pantelis Antoniou
2015-04-24 20:31 ` Greg KH
2015-04-27 17:51 ` Pantelis Antoniou
2015-04-27 18:11 ` Greg KH [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=20150427181138.GA27043@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@secretlab.ca \
--cc=koen@dominion.thruhere.net \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mporter@konsulko.com \
--cc=panto@antoniou-consulting.com \
--cc=robherring2@gmail.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