From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751684AbdF0FVo (ORCPT <rfc822;w@1wt.eu>);
        Tue, 27 Jun 2017 01:21:44 -0400
Received: from mail-pg0-f67.google.com ([74.125.83.67]:32887 "EHLO
        mail-pg0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751473AbdF0FVi (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 27 Jun 2017 01:21:38 -0400
From: Palmer Dabbelt <palmer@dabbelt.com>
To: tglx@linutronix.de
To: jason@lakedaemon.net
To: marc.zyngier@arm.com
To: robh+dt@kernel.org
To: mark.rutland@arm.com
To: jic23@kernel.org
To: treding@nvidia.com
To: maxime.ripard@free-electrons.com
To: marek.vasut@gmail.com
To: ccc94453@vip.cybercity.dk
To: gregkh@linuxfoundation.org
To: linux-kernel@vger.kernel.org
To: devicetree@vger.kernel.org
Subject: RISC-V Device Tree Documentation
Date: Mon, 26 Jun 2017 22:21:21 -0700
Message-Id: <20170627052124.426-1-palmer@dabbelt.com>
X-Mailer: git-send-email 2.13.0
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

As part of submitting the RISC-V Linux port it was suggested that we write some
documentation that describes our device tree bindings.  Our port is still in
progress, but it was suggested that we start sending patches to the relevant
parties.  There is one outstanding issue to resolve with the PLIC bindings, but
I think the other two patches should be sane.