From: Sudeep Holla <sudeep.holla@arm.com>
To: Jolly Shah <jolly.shah@xilinx.com>,
michal.simek@xilinx.com, linux-clk@vger.kernel.org
Cc: mturquette@baylibre.com, sboyd@codeaurora.org,
Sudeep Holla <sudeep.holla@arm.com>,
Jolly Shah <jollys@xilinx.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 0/2] drivers: clk: Add ZynqMP clock driver support
Date: Thu, 11 Jan 2018 10:54:39 +0000 [thread overview]
Message-ID: <6004ad81-96f1-34d9-a037-2c355720dc08@arm.com> (raw)
In-Reply-To: <1515449797-5629-1-git-send-email-jollys@xilinx.com>
On 08/01/18 22:16, Jolly Shah wrote:
> Add clock driver for ZynqMP
>
Can you post the complete series in one set for easy of review. It's
currently broken into *6 - 8* different sets by different authors and
it's extremely hard to get the full view of how these pieces are
connected and extremely misleading. Can someone post them collectively
as you would already have it if you are doing some testing building on
each patch set.
IIUC mailbox is used for all the communication, right ?
If so, to start with just have 2 series one for mailbox/transport and
another for the whole protocol(eemi?) and users of it.
--
Regards,
Sudeep
next prev parent reply other threads:[~2018-01-11 10:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 22:16 Jolly Shah
2018-01-08 22:16 ` [RFC PATCH 1/2] drivers: clk: Add clk_get_children support Jolly Shah
2018-01-08 22:16 ` [RFC PATCH 2/2] drivers: clk: Add ZynqMP clock driver Jolly Shah
2018-01-09 12:52 ` Philippe Ombredanne
2018-01-10 20:06 ` Jolly Shah
2018-01-10 20:15 ` Jolly Shah
2018-01-11 10:54 ` Sudeep Holla [this message]
2018-01-11 20:29 ` [RFC PATCH 0/2] drivers: clk: Add ZynqMP clock driver support Jolly Shah
2018-01-12 11:47 ` Sudeep Holla
2018-01-12 23:52 ` Jolly Shah
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=6004ad81-96f1-34d9-a037-2c355720dc08@arm.com \
--to=sudeep.holla@arm.com \
--cc=jolly.shah@xilinx.com \
--cc=jollys@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=mturquette@baylibre.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®