From: Ralf Baechle <ralf@linux-mips.org>
To: Purna Chandra Mandal <purna.mandal@microchip.com>
Cc: linux-kernel@vger.kernel.org, linux-mips@linux-mips.org,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.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>,
Pawel Moll <pawel.moll@arm.com>,
Sandeep Sheriker <sandeepsheriker.mallikarjun@microchip.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v11 0/3] PIC32MZDA Clock Driver
Date: Fri, 13 May 2016 14:18:33 +0200 [thread overview]
Message-ID: <20160513121833.GC4215@linux-mips.org> (raw)
In-Reply-To: <1463125961-10706-1-git-send-email-purna.mandal@microchip.com>
On Fri, May 13, 2016 at 01:22:38PM +0530, Purna Chandra Mandal wrote:
Thanks for resolving the remaining issues. As per discussion of the
last version I've now queued the entire series for 4.7.
One step closer to full PIC32MZDA in-tree support!
Ralf
prev parent reply other threads:[~2016-05-13 12:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 7:52 [PATCH v11 0/3] PIC32MZDA Clock Driver Purna Chandra Mandal
2016-05-13 7:52 ` Purna Chandra Mandal
2016-05-13 7:52 ` Purna Chandra Mandal
2016-05-13 7:52 ` [PATCH v11 1/3] dt/bindings/clk: Add PIC32 clock binding documentation Purna Chandra Mandal
2016-05-13 7:52 ` Purna Chandra Mandal
2016-05-13 7:52 ` [PATCH v11 2/3] clk: microchip: Add Microchip PIC32 clock driver Purna Chandra Mandal
2016-05-13 7:52 ` Purna Chandra Mandal
2016-05-13 7:52 ` [PATCH v11 3/3] MIPS: dts: pic32: Update dts to reflect new PIC32MZDA clk binding Purna Chandra Mandal
2016-05-13 7:52 ` Purna Chandra Mandal
2016-05-13 12:18 ` Ralf Baechle [this message]
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=20160513121833.GC4215@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=joshua.henderson@microchip.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=pawel.moll@arm.com \
--cc=purna.mandal@microchip.com \
--cc=robh+dt@kernel.org \
--cc=sandeepsheriker.mallikarjun@microchip.com \
--cc=sboyd@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.