From: Greg KH <gregkh@linuxfoundation.org>
To: "Marty E. Plummer" <hanetzer@startmail.com>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
xuejiancheng@hisilicon.com, leo.yan@linaro.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
mark.rutland@arm.com, mturquette@baylibre.com,
wenpan@hisilicon.com, robh+dt@kernel.org, linux@armlinux.org.uk,
sboyd@codeaurora.org, xuwei5@hisilicon.com,
zhangfei.gao@linaro.org, arnd@arndb.de
Subject: Re: [RFC RESEND 0/3] Add support for Hisilicon Hi3521A SoC
Date: Mon, 18 Sep 2017 12:55:20 +0200 [thread overview]
Message-ID: <20170918105520.GA2837@kroah.com> (raw)
In-Reply-To: <20170917082327.10058-1-hanetzer@startmail.com>
On Sun, Sep 17, 2017 at 03:23:24AM -0500, Marty E. Plummer wrote:
> Greetings,
>
> I'd like the community's feedback on the following patchset. I've attempted to
> split my changes up in what I believe to be a sensible setup.
>
> The device I'm working against is the 'SamsungSV SDR-B74301' HD CCTV surveillance
> system, which uses a Hisilicon Hi3521A arm SoC as its basis.
>
> Resending due to a typo, s/primcell/primecell/
>
> Marty E. Plummer (3):
> clk: hisilicon: add CRG driver Hi3521A SoC
> arm: hisi: enable Hi3521A SoC
> arm: dts: add Hi3521A dts
Seems reasonable to me, but I'll let the clk maintainers/developers give
you a better review...
thanks,
greg k-h
prev parent reply other threads:[~2017-09-18 10:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 8:23 [RFC RESEND 0/3] Add support for Hisilicon Hi3521A SoC Marty E. Plummer
2017-09-17 8:23 ` [RFC RESEND 1/3] clk: hisilicon: add CRG driver " Marty E. Plummer
2017-09-17 8:23 ` [RFC RESEND 2/3] arm: hisi: enable " Marty E. Plummer
2017-09-17 8:23 ` [RFC RESEND 3/3] arm: dts: add Hi3521A dts Marty E. Plummer
[not found] ` <20170917082327.10058-4-hanetzer-zVALfsKDk1AS+FvcfC7Uqw@public.gmane.org>
2017-09-20 20:53 ` Rob Herring
2017-09-20 23:04 ` Marty E. Plummer
[not found] ` <20170920230405.tz3vzoys2vn72rgv-1hXBbFsFebEOoWXT+9nehYcPyU6MP8rFhTcysPvq43Q@public.gmane.org>
2017-09-21 1:08 ` Rob Herring
2017-09-21 2:15 ` Marty E. Plummer
2017-09-18 10:55 ` Greg KH [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=20170918105520.GA2837@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=hanetzer@startmail.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=wenpan@hisilicon.com \
--cc=xuejiancheng@hisilicon.com \
--cc=xuwei5@hisilicon.com \
--cc=zhangfei.gao@linaro.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).