From: Michal Simek <michal.simek@xilinx.com>
To: Philipp Zabel <p.zabel@pengutronix.de>,
Nava kishore Manne <nava.manne@xilinx.com>, <robh+dt@kernel.org>,
<mark.rutland@arm.com>, <michal.simek@xilinx.com>,
<rajanv@xilinx.com>, <jollys@xilinx.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <chinnikishore369@gmail.com>
Subject: Re: [PATCH v3 1/3] firmware: xilinx: Add reset API's
Date: Thu, 24 Jan 2019 10:49:21 +0100 [thread overview]
Message-ID: <e0f6e1d3-e443-040e-8c07-79359e2af37a@xilinx.com> (raw)
In-Reply-To: <1548322989.6014.4.camel@pengutronix.de>
On 24. 01. 19 10:43, Philipp Zabel wrote:
> On Fri, 2019-01-25 at 13:16 +0530, Nava kishore Manne wrote:
>> This Patch Adds reset API's to support release, assert
>> and status functionalities by using firmware interface.
>>
>> Signed-off-by: Nava kishore Manne <nava.manne@xilinx.com>
>
> Michal, Should I merge this through the reset tree together with the
> reset driver?
It would be better if this goes via my tree. There is at least one
series which also touches the same parts in these files that's why there
will be collisions.
If you can review that I will take it via my tree and arm-soc guys to
mainline.
Thanks,
Michal
next prev parent reply other threads:[~2019-01-24 9:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 7:46 [PATCH v3 0/3] Add reset driver support for ZynqMP Nava kishore Manne
2019-01-25 7:46 ` [PATCH v3 1/3] firmware: xilinx: Add reset API's Nava kishore Manne
2019-01-24 9:43 ` Philipp Zabel
2019-01-24 9:49 ` Michal Simek [this message]
2019-01-24 10:10 ` Philipp Zabel
2019-01-25 7:46 ` [PATCH v3 2/3] dt-bindings: reset: Add bindings for ZynqMP reset driver Nava kishore Manne
2019-01-25 7:46 ` [PATCH v3 3/3] reset: reset-zynqmp: Adding support for Xilinx zynqmp reset controller Nava kishore Manne
2019-01-29 13:10 ` [PATCH v3 0/3] Add reset driver support for ZynqMP Michal Simek
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=e0f6e1d3-e443-040e-8c07-79359e2af37a@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=chinnikishore369@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jollys@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nava.manne@xilinx.com \
--cc=p.zabel@pengutronix.de \
--cc=rajanv@xilinx.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
all inboxes | Powered by JetHome®