From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_PASS,URIBL_BLOCKED,USER_AGENT_NEOMUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 99FE2C43387 for ; Thu, 10 Jan 2019 23:56:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5AF8E2133F for ; Thu, 10 Jan 2019 23:56:47 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=brauner.io header.i=@brauner.io header.b="gBRGjVEz" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730614AbfAJX4q (ORCPT ); Thu, 10 Jan 2019 18:56:46 -0500 Received: from mail-ed1-f68.google.com ([209.85.208.68]:38862 "EHLO mail-ed1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730560AbfAJX4p (ORCPT ); Thu, 10 Jan 2019 18:56:45 -0500 Received: by mail-ed1-f68.google.com with SMTP id h50so11676201ede.5 for ; Thu, 10 Jan 2019 15:56:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brauner.io; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=RKKaQjsv4Ps4QaDXlz2Kbrdhx+3vq2p7DIwKilUCu+Q=; b=gBRGjVEzzHHjs9Kxz9qmjwlS5rAvNpHKHMR3j/RRzNVi/SPcY80c/QR0kyrpydTTJc BvCIyYA/TUbDdSBr79ZMnynMno49ttXggigjsRi0P6bv+Bv9wEI7Rgkg7d0SSnbWAD42 hSH/V6tnPstdTLVnNhC/PCNUMtG1eHChIol7c1YDPm8/PMUmU6eFwwU5Jmd+7prinoc7 dr+lurmvEn72/Swf4TUZ2kXMwv7R+7ukEmnp6I3luCMOkn7g0BMhoQxGSm9qJnbEGM3a bwJ3xa7mJPzf5mCqJlOsrqIpkYSOtIpmptoZzyet6wKbBDcuJMbVdPq4mvCbVBVBt0HY xXNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=RKKaQjsv4Ps4QaDXlz2Kbrdhx+3vq2p7DIwKilUCu+Q=; b=bmhADb1KguUaiiNUCcCfY4pmLKf53QWOkyeFEN9Gx/igDh7sKonOptWPXpE8Lw8dzc 1zZgqYoRdYY/C2UB3/dt9I8IRg3tRNaza1rHTIqkFdCnIndPc/4awUehUE6N5wd547Ya NX6grlV1m2QrwrgmOkiCN1FaXvtab5y3ZiWcmBQryrN044XL7LMqcKGxCBGFfuoglETb teYIhU9Psocd/F8zeHXThXNdPEkqOHDZJIC0UMqkNn5LrKuZ/Y1+3s1mEHyhbYqoEfmA w0LufuPxEUcMQFUSa2+reHBOjBCRfMufvqHlhxPJn2mua7+E0n59djEalRPQwDOFk6QZ B4PQ== X-Gm-Message-State: AJcUuke/M0tZON9w4AukfZ3VMuxoYfpOCVJgme2W32AWeda6MCyx/uh6 eU8fMFsEKaCC3opAkgLNh1XQNg6LNrzLqg== X-Google-Smtp-Source: ALg8bN7rq9a7f+WdmQbMa9wdhL1PSWJKfVTuLPmAwNg2Ogw9husPRUqNAVwq5e309XaqeQvm+XBhMg== X-Received: by 2002:a17:906:20c2:: with SMTP id c2-v6mr8085291ejc.241.1547164603532; Thu, 10 Jan 2019 15:56:43 -0800 (PST) Received: from brauner.io ([2a02:8109:b6c0:d6c:c571:88:8aee:976c]) by smtp.gmail.com with ESMTPSA id e35sm2075779eda.13.2019.01.10.15.56.42 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 10 Jan 2019 15:56:43 -0800 (PST) Date: Fri, 11 Jan 2019 00:56:42 +0100 From: Christian Brauner To: Jonathan Corbet Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] Documentation/filesystems: add binderfs Message-ID: <20190110235641.nhuodos74i67jf64@brauner.io> References: <20190110231309.12653-1-christian@brauner.io> <20190110164703.1dd6cee1@lwn.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190110164703.1dd6cee1@lwn.net> User-Agent: NeoMutt/20180716 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 10, 2019 at 04:47:03PM -0700, Jonathan Corbet wrote: > On Fri, 11 Jan 2019 00:13:09 +0100 > Christian Brauner 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 > > Seems like a worthwhile addition overall. I know nothing about binderfs, > so can't speak to the accuracy, of course. I do have a couple of > metacomments, though: > > - Please consider doing this in RST and tying it into our documentation > tree. It's *almost* RST now, so the effort required will be almost > zero. Oh sure. I simply didn't know. I was just going by the files under Documentation/filesystems/. Is this a separate git tree? If so, where is located? Or can I just place it as Documentation/filesystems/binderfs.rst? > > - It should probably have an SPDX line at the top. Yup, can add. > > - Is it worth putting the example program in the samples/ directory? Is > it something that would ever make any sense to run in its current form? Hm, I mean I can write a small binary that illustrates mounting and allocating binder devices in binderfs. Thanks! Christian