From: Linus Walleij <linus.walleij@linaro.org>
To: Purna Chandra Mandal <purna.mandal@microchip.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux MIPS <linux-mips@linux-mips.org>,
Ralf Baechle <ralf@linux-mips.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Kumar Gala <galak@codeaurora.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Rob Herring <robh+dt@kernel.org>,
Joshua Henderson <joshua.henderson@microchip.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH 07/11] dt/bindings: Correct clk binding example for PIC32 pinctrl
Date: Thu, 26 May 2016 10:37:20 +0200 [thread overview]
Message-ID: <CACRpkdZPHd2G+LRu5WJBDOu2rjWBqprqYYbfTnOQhXpkT3g=dQ@mail.gmail.com> (raw)
In-Reply-To: <1463461560-9629-7-git-send-email-purna.mandal@microchip.com>
On Tue, May 17, 2016 at 7:05 AM, Purna Chandra Mandal
<purna.mandal@microchip.com> wrote:
> Update binding example based on new clock binding scheme.
> [1] Documentation/devicetree/bindings/clock/microchip,pic32.txt
>
> Signed-off-by: Purna Chandra Mandal <purna.mandal@microchip.com>
Patch applied to the pinctrl tree with Rob's ACK.
Yours,
Linus Walleij
next prev parent reply other threads:[~2016-05-26 8:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 5:05 [PATCH 01/11] clk: microchip: use readl_poll_timeout() in pbclk_set_rate() Purna Chandra Mandal
2016-05-17 5:05 ` [PATCH 02/11] clk: microchip: Initialize SOSC clock rate for PIC32MZDA Purna Chandra Mandal
2016-08-24 23:05 ` Stephen Boyd
2016-05-17 5:05 ` [PATCH 03/11] MIPS: pic32mzda: fix getting timer clock rate Purna Chandra Mandal
2016-05-17 12:30 ` Ralf Baechle
2016-05-25 16:02 ` Harvey Hunt
2016-06-02 5:05 ` Purna Chandra Mandal
2016-05-17 5:05 ` [PATCH 04/11] irqchip: irq-pic32-evic: Fix bug with external interrupts Purna Chandra Mandal
2016-05-17 8:09 ` Marc Zyngier
2016-05-17 5:05 ` [PATCH 05/11] serial: pic32_uart: Fix double free of 'sport->irq_fault_name' Purna Chandra Mandal
2016-05-17 5:05 ` [PATCH 06/11] dt/bindings: Correct clk binding example for PIC32 SDHCI Purna Chandra Mandal
2016-05-18 16:50 ` Rob Herring
2016-05-17 5:05 ` [PATCH 07/11] dt/bindings: Correct clk binding example for PIC32 pinctrl Purna Chandra Mandal
2016-05-18 16:50 ` Rob Herring
2016-05-26 8:37 ` Linus Walleij [this message]
2016-05-17 5:05 ` [PATCH 08/11] dt/bindings: Correct clk binding example for PIC32 serial Purna Chandra Mandal
2016-05-18 16:51 ` Rob Herring
2016-05-17 5:05 ` [PATCH 09/11] dt/bindings: Correct clk binding example for PIC32 DMT Purna Chandra Mandal
2016-05-18 16:51 ` Rob Herring
2016-05-17 5:05 ` [PATCH 10/11] dt/bindings: Correct clk binding example for PIC32 WDT Purna Chandra Mandal
2016-05-18 16:52 ` Rob Herring
2016-05-17 5:06 ` [PATCH 11/11] dt/bindings: Correct clk binding example for PIC32 gpio Purna Chandra Mandal
2016-05-18 16:52 ` Rob Herring
2016-05-26 8:38 ` Linus Walleij
2016-08-24 23:05 ` [PATCH 01/11] clk: microchip: use readl_poll_timeout() in pbclk_set_rate() Stephen Boyd
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='CACRpkdZPHd2G+LRu5WJBDOu2rjWBqprqYYbfTnOQhXpkT3g=dQ@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=joshua.henderson@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mark.rutland@arm.com \
--cc=purna.mandal@microchip.com \
--cc=ralf@linux-mips.org \
--cc=robh+dt@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).