From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Stewart Smith <stewart@linux.vnet.ibm.com>,
Rob Herring <robh+dt@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Cyril Bur <cyrilbur@gmail.com>,
William Kennington <wak@google.com>
Subject: Re: [PATCH] mtd: powernv: Support MTD_NO_ERASE
Date: Mon, 30 Oct 2017 09:48:29 +0100 [thread overview]
Message-ID: <20171030094829.63730a19@bbrezillon> (raw)
In-Reply-To: <87k1zt82gq.fsf@linux.vnet.ibm.com>
On Wed, 18 Oct 2017 16:11:33 +1100
Stewart Smith <stewart@linux.vnet.ibm.com> wrote:
> Rob Herring <robh+dt@kernel.org> writes:
> > I'd prefer they be documented in the kernel especially if they are
> > used by the kernel. Of course, there's IBM bindings covered by various
> > ?PAPR specs which wouldn't make sense to duplicate, but I'm guessing
> > what's documented in skiboot are not covered by those specs.
>
> Correct.
>
> I don't have an objection to docs being in both places, as long as we
> could keep both in sync. Would suitable comments in the RST doc files
> pointing to the skiboot repo as the canonical copy work?
Rob, any opinion on that?
>
> I'd like to be able to just diff a subtree of kernel and skiboot to see
> if the docs have diverged.
>
> We may also need to think of a way to ensure that any of that moving
> back/forth of edits is done in a way that makes licensing sense too
> (skiboot is Apache 2.0)
>
next prev parent reply other threads:[~2017-10-30 8:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 20:23 [PATCH] mtd: powernv: Support MTD_NO_ERASE William A. Kennington III
2017-09-21 7:59 ` Boris Brezillon
[not found] ` <CAPnigKmBujCoKdtXwnK6YsU=YvXM+MaDvDvKpUXEVgHzOC-VEw@mail.gmail.com>
2017-09-22 4:13 ` Michael Ellerman
2017-10-16 15:55 ` Boris Brezillon
2017-10-17 13:21 ` Rob Herring
2017-10-18 5:11 ` Stewart Smith
2017-10-30 8:48 ` Boris Brezillon [this message]
2017-10-30 15:23 ` Rob Herring
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=20171030094829.63730a19@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=cyrilbur@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mpe@ellerman.id.au \
--cc=robh+dt@kernel.org \
--cc=stewart@linux.vnet.ibm.com \
--cc=wak@google.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