linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Christian Brauner <christian@brauner.io>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] Documentation/filesystems: add binderfs
Date: Mon, 14 Jan 2019 17:24:01 -0700	[thread overview]
Message-ID: <20190114172401.018afb9c@lwn.net> (raw)
In-Reply-To: <20190111134100.24095-1-christian@brauner.io>

On Fri, 11 Jan 2019 14:40:59 +0100
Christian Brauner <christian@brauner.io> wrote:

> This documents the Android binderfs filesystem used to dynamically add and
> remove binder devices that are private to each instance.
> 
> Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com>

Two quick notes:

> ---
> /* Changelog */
> v1:
> - switch from *.txt to *.rst format
> ---
>  Documentation/filesystems/binderfs.rst | 70 ++++++++++++++++++++++++++
>  1 file changed, 70 insertions(+)
>  create mode 100644 Documentation/filesystems/binderfs.rst

You didn't add it to index.rst, so it won't actually become part of the
docs build.

> diff --git a/Documentation/filesystems/binderfs.rst b/Documentation/filesystems/binderfs.rst
> new file mode 100644
> index 000000000000..74a744b42db7
> --- /dev/null
> +++ b/Documentation/filesystems/binderfs.rst
> @@ -0,0 +1,70 @@
> +.. SPDX-License-Identifier: GPL-2.0
> +
> +The Android binderfs Filesystem
> +===============================
> +
> +Android binderfs is a filesystem for the Android binder IPC mechanism.  It
> +allows to dynamically add and remove binder devices at runtime.  Binder devices
> +located in a new binderfs instance are independent of binder devices located in
> +other binderfs instances.  Mounting a new binderfs instance makes it possible
> +to get a set of private binder devices.
> +
> +Mounting binderfs
> +-----------------
> +
> +Android binderfs can be mounted with:
> +
> +::

This can be more readably formatted as:

	Android binderfs can be mounted with::

I've applied the patches, taking the liberty of fixing both of those
things up.  Thanks!

jon

  parent reply	other threads:[~2019-01-15  0:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11 13:40 [PATCH v1 1/2] Documentation/filesystems: add binderfs Christian Brauner
2019-01-11 13:41 ` [PATCH v1 2/2] samples: add binderfs sample program Christian Brauner
2019-01-15  0:24 ` Jonathan Corbet [this message]
2019-01-15  8:59   ` [PATCH v1 1/2] Documentation/filesystems: add binderfs Christian Brauner
2019-07-02 17:57   ` Matthew Wilcox
2019-07-02 19:51     ` Christian Brauner
2019-07-08 20:16     ` Jonathan Corbet

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=20190114172401.018afb9c@lwn.net \
    --to=corbet@lwn.net \
    --cc=christian@brauner.io \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).