linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Vabhav Sharma <vabhav.sharma@nxp.com>,
	arnd@arndb.de, catalin.marinas@arm.com,
	devicetree@vger.kernel.org, gregkh@linuxfoundation.org,
	kstewart@linuxfoundation.org,
	linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
	linux-kernel-owner@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	mark.rutland@arm.com, mturquette@baylibre.com, oss@buserror.net,
	rjw@rjwysocki.net, robh+dt@kernel.org, sudeep.holla@arm.com,
	viresh.kumar@linaro.org, will.deacon@arm.com,
	yamada.masahiro@socionext.com
Cc: linux@armlinux.org.uk, V.Sethi@nxp.com, udit.kumar@nxp.com,
	Yogesh Gaur <yogeshnarayan.gaur@nxp.com>,
	Tang Yuantian <andy.tang@nxp.com>,
	Vabhav Sharma <vabhav.sharma@nxp.com>
Subject: Re: [PATCH v3 4/6] drivers: clk-qoriq: Add clockgen support for lx2160a
Date: Mon, 01 Oct 2018 15:04:24 -0700	[thread overview]
Message-ID: <153843146463.119890.6551025813220021124@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <1537747741-6245-5-git-send-email-vabhav.sharma@nxp.com>

Same subject comment.

Quoting Vabhav Sharma (2018-09-23 17:08:59)
> From: Yogesh Gaur <yogeshnarayan.gaur@nxp.com>
> 
> Add clockgen support for lx2160a.

  reply	other threads:[~2018-10-01 22:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-24  0:08 [PATCH v3 0/6] arm64: dts: NXP: add basic dts file for LX2160A SoC Vabhav Sharma
2018-09-24  0:08 ` [PATCH v3 1/6] dt-bindings: arm64: add compatible for LX2160A Vabhav Sharma
2018-09-27 19:32   ` Rob Herring
2018-09-24  0:08 ` [PATCH v3 2/6] soc/fsl/guts: Add compatible string " Vabhav Sharma
2018-09-24  0:08 ` [PATCH v3 3/6] drivers: clk-qoriq: increase array size of cmux_to_group Vabhav Sharma
2018-10-01 22:04   ` Stephen Boyd
2018-10-03 14:25     ` Vabhav Sharma
2018-09-24  0:08 ` [PATCH v3 4/6] drivers: clk-qoriq: Add clockgen support for lx2160a Vabhav Sharma
2018-10-01 22:04   ` Stephen Boyd [this message]
2018-10-03 14:25     ` Vabhav Sharma
2018-09-24  0:09 ` [PATCH v3 5/6] arm64: dts: add QorIQ LX2160A SoC support Vabhav Sharma
2018-09-28 20:41   ` Li Yang
2018-10-01 12:19     ` Vabhav Sharma
2018-09-24  0:09 ` [PATCH v3 6/6] arm64: dts: add LX2160ARDB board support Vabhav Sharma
2018-09-28 19:37   ` Li Yang
2018-10-01 12:26     ` Vabhav Sharma

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=153843146463.119890.6551025813220021124@swboyd.mtv.corp.google.com \
    --to=sboyd@kernel.org \
    --cc=V.Sethi@nxp.com \
    --cc=andy.tang@nxp.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel-owner@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mark.rutland@arm.com \
    --cc=mturquette@baylibre.com \
    --cc=oss@buserror.net \
    --cc=rjw@rjwysocki.net \
    --cc=robh+dt@kernel.org \
    --cc=sudeep.holla@arm.com \
    --cc=udit.kumar@nxp.com \
    --cc=vabhav.sharma@nxp.com \
    --cc=viresh.kumar@linaro.org \
    --cc=will.deacon@arm.com \
    --cc=yamada.masahiro@socionext.com \
    --cc=yogeshnarayan.gaur@nxp.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;
as well as URLs for NNTP newsgroup(s).