From: Marek Vasut <marex@denx.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: linux-mips@linux-mips.org, Wills Wang <wills.wang@live.com>,
Daniel Schwierzeck <daniel.schwierzeck@gmail.com>,
Alban Bedel <albeu@free.fr>, Gabor Juhos <juhosg@openwrt.org>
Subject: Re: [RFC v5 03/15] MIPS: ath79: use clk-ath79.c driver for AR933X
Date: Tue, 9 Feb 2016 12:07:47 +0100 [thread overview]
Message-ID: <201602091207.47155.marex@denx.de> (raw)
In-Reply-To: <1455005641-7079-4-git-send-email-antonynpavlov@gmail.com>
On Tuesday, February 09, 2016 at 09:13:49 AM, Antony Pavlov wrote:
> Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com>
> Cc: Gabor Juhos <juhosg@openwrt.org>
> Cc: Alban Bedel <albeu@free.fr>
> Cc: linux-mips@linux-mips.org
Acked-by: Marek Vasut <marex@denx.de>
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-02-09 11:24 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 8:13 [RFC v5 00/15] MIPS: ath79: AR9331: add devicetree support Antony Pavlov
2016-02-09 8:13 ` [RFC v5 01/15] WIP: clk: add Atheros AR933X SoCs clock driver Antony Pavlov
2016-02-09 11:05 ` Marek Vasut
2016-02-09 21:51 ` Alban
2016-02-11 12:50 ` Antony Pavlov
2016-02-12 2:21 ` Michael Turquette
2016-02-09 8:13 ` [RFC v5 02/15] dt-bindings: clock: qca,ath79-pll: fix copy-paste typos Antony Pavlov
2016-02-09 11:05 ` Marek Vasut
2016-02-09 21:52 ` Alban
2016-02-12 14:52 ` Rob Herring
2016-02-09 8:13 ` [RFC v5 03/15] MIPS: ath79: use clk-ath79.c driver for AR933X Antony Pavlov
2016-02-09 11:07 ` Marek Vasut [this message]
2016-02-09 22:07 ` Alban
2016-02-10 9:04 ` Antony Pavlov
2016-02-09 8:13 ` [RFC v5 04/15] WIP: MIPS: ath79: setup.c: disable platform code for OF boards Antony Pavlov
2016-02-09 11:08 ` Marek Vasut
2016-02-09 8:13 ` [RFC v5 05/15] MIPS: dts: qca: introduce AR9331 devicetree Antony Pavlov
2016-02-09 11:12 ` Marek Vasut
2016-02-09 8:13 ` [RFC v5 06/15] MIPS: ath79: add initial support for TP-LINK MR3020 Antony Pavlov
2016-02-09 11:13 ` Marek Vasut
2016-02-09 8:13 ` [RFC v5 07/15] usb: ehci: add vbus-gpio parameter Antony Pavlov
2016-02-09 11:14 ` Marek Vasut
2016-02-09 22:15 ` Alban
2016-02-10 0:00 ` Antony Pavlov
2016-02-18 16:12 ` Alan Stern
2016-02-18 16:12 ` Alan Stern
2016-02-18 16:39 ` Marek Vasut
2016-02-18 18:06 ` Antony Pavlov
2016-02-18 18:06 ` Antony Pavlov
2016-02-18 18:31 ` Sergei Shtylyov
2016-02-18 22:11 ` Antony Pavlov
2016-02-09 8:13 ` [RFC v5 08/15] MIPS: tl_mr3020: enable usb support Antony Pavlov
2016-02-09 8:13 ` [RFC v5 09/15] devicetree: add Dragino vendor id Antony Pavlov
2016-02-09 8:13 ` [RFC v5 10/15] MIPS: ath79: add initial support for Dragino MS14 (Dragino 2) Antony Pavlov
2016-02-09 11:16 ` Marek Vasut
2016-02-09 8:13 ` [RFC v5 11/15] devicetree: add Onion Corporation vendor id Antony Pavlov
2016-02-09 8:13 ` [RFC v5 12/15] MIPS: ath79: add initial support for Onion Omega Antony Pavlov
2016-02-09 8:13 ` [RFC v5 13/15] devicetree: add DPTechnics vendor id Antony Pavlov
2016-02-12 14:53 ` Rob Herring
2016-02-09 8:14 ` [RFC v5 14/15] MIPS: ath79: add DPT-Module support Antony Pavlov
2016-02-09 8:14 ` [RFC v5 15/15] WIP: MIPS: ath79: add AR9331 devicetree defconfig Antony Pavlov
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=201602091207.47155.marex@denx.de \
--to=marex@denx.de \
--cc=albeu@free.fr \
--cc=antonynpavlov@gmail.com \
--cc=daniel.schwierzeck@gmail.com \
--cc=juhosg@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=wills.wang@live.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