public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hauke Mehrtens <hauke@hauke-m.de>
To: Jon Mason <jonmason@broadcom.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Russell King <linux@arm.linux.org.uk>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH v3 1/3] ARM: dts: enable clock support for BCM5301X
Date: Sat, 21 Nov 2015 15:26:09 +0100	[thread overview]
Message-ID: <56507F01.8080807@hauke-m.de> (raw)
In-Reply-To: <1448032640-27713-2-git-send-email-jonmason@broadcom.com>

On 11/20/2015 04:17 PM, Jon Mason wrote:
> Replace current device tree dummy clocks with real clock support for
> Broadcom Northstar SoCs.
> 
> Signed-off-by: Jon Mason <jonmason@broadcom.com>
> ---
>  arch/arm/boot/dts/bcm5301x.dtsi | 92 +++++++++++++++++++++++++++++++----------
>  1 file changed, 71 insertions(+), 21 deletions(-)
> 

Acked-by: Hauke Mehrtens <hauke@hauke-m.de>


  reply	other threads:[~2015-11-21 14:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 15:17 [PATCH v3 0/3] ARM: dts: add support for NS, NSP, and NS2 clocks Jon Mason
2015-11-20 15:17 ` [PATCH v3 1/3] ARM: dts: enable clock support for BCM5301X Jon Mason
2015-11-21 14:26   ` Hauke Mehrtens [this message]
2015-11-20 15:17 ` [PATCH v3 2/3] ARM: dts: enable clock support for Broadcom NSP Jon Mason
2015-11-20 15:17 ` [PATCH v3 3/3] ARM64: dts: enable clock support for Broadcom NS2 Jon Mason
2015-11-20 17:12 ` [PATCH v3 0/3] ARM: dts: add support for NS, NSP, and NS2 clocks Ray Jui
2015-11-20 18:16 ` Florian Fainelli

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=56507F01.8080807@hauke-m.de \
    --to=hauke@hauke-m.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=jonmason@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --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