From: Mark Brown <broonie@kernel.org>
To: Yash Shah <yash.shah@sifive.com>
Cc: linux-pwm@vger.kernel.org, peter@korsgaard.com,
aou@eecs.berkeley.edu, sachin.ghadi@sifive.com,
devicetree@vger.kernel.org, gregkh@linuxfoundation.org,
bgolaszewski@baylibre.com, paul.walmsley@sifive.com,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
linux-spi@vger.kernel.org, linux-gpio@vger.kernel.org,
thierry.reding@gmail.com, andrew@lunn.ch,
linux-i2c@vger.kernel.org, linux-serial@vger.kernel.org,
u.kleine-koenig@pengutronix.de, palmer@dabbelt.com,
linux-riscv@lists.infradead.org, lee.jones@linaro.org,
linus.walleij@linaro.org
Subject: Re: [PATCH 1/4] dt-bindings: riscv: Update DT binding docs to support SiFive FU740 SoC
Date: Wed, 2 Dec 2020 13:04:53 +0000 [thread overview]
Message-ID: <20201202130452.GC5560@sirena.org.uk> (raw)
In-Reply-To: <1606896236-62780-2-git-send-email-yash.shah@sifive.com>
[-- Attachment #1.1: Type: text/plain, Size: 787 bytes --]
On Wed, Dec 02, 2020 at 01:33:53PM +0530, Yash Shah wrote:
> ---
> Documentation/devicetree/bindings/gpio/sifive,gpio.yaml | 4 +++-
> Documentation/devicetree/bindings/i2c/i2c-ocores.txt | 6 ++++--
> Documentation/devicetree/bindings/pwm/pwm-sifive.yaml | 9 ++++++---
> Documentation/devicetree/bindings/riscv/cpus.yaml | 6 ++++++
> Documentation/devicetree/bindings/serial/sifive-serial.yaml | 4 +++-
> Documentation/devicetree/bindings/spi/spi-sifive.yaml | 10 ++++++----
> 6 files changed, 28 insertions(+), 11 deletions(-)
The driver bindings for the various subsystems would normally be sent as
independent patches to those subsystems. Driver changes mostly get
reviewed by subsystem maintainers rather than architecture maintainers.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2020-12-02 13:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 8:03 [PATCH 0/4] arch: riscv: add board and SoC DT file support Yash Shah
2020-12-02 8:03 ` [PATCH 1/4] dt-bindings: riscv: Update DT binding docs to support SiFive FU740 SoC Yash Shah
2020-12-02 13:04 ` Mark Brown [this message]
2020-12-02 14:58 ` Andrew Lunn
2020-12-03 6:36 ` Yash Shah
2020-12-02 8:03 ` [PATCH 2/4] riscv: dts: add initial support for the SiFive FU740-C000 SoC Yash Shah
2020-12-02 8:03 ` [PATCH 3/4] dt-bindings: riscv: Update YAML doc to support SiFive HiFive Unmatched board Yash Shah
2020-12-02 8:03 ` [PATCH 4/4] riscv: dts: add initial board data for the SiFive HiFive Unmatched Yash Shah
2020-12-03 0:43 ` kernel test robot
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=20201202130452.GC5560@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andrew@lunn.ch \
--cc=aou@eecs.berkeley.edu \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peter@korsgaard.com \
--cc=robh+dt@kernel.org \
--cc=sachin.ghadi@sifive.com \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=yash.shah@sifive.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;
as well as URLs for NNTP newsgroup(s).