From: Michal Simek <michal.simek@xilinx.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Nava kishore Manne <nava.manne@xilinx.com>, <robh+dt@kernel.org>,
<mark.rutland@arm.com>, <michal.simek@xilinx.com>,
<jollys@xilinx.com>, <rajanv@xilinx.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] firmware: xilinx: Add zynqmp_pm_get_chipid() API
Date: Tue, 5 Feb 2019 11:29:02 +0100 [thread overview]
Message-ID: <f317c341-9706-3a24-6faf-711f2627bcce@xilinx.com> (raw)
In-Reply-To: <d949520b-452f-9e66-42ae-263959a8c549@linaro.org>
Hi,
On 03. 02. 19 9:50, Srinivas Kandagatla wrote:
> Hi Kishore,
>
> I need ack for this patch from Michal Simek to take this via nvmem tree.
not sure if my reaction went through. Just for a record. There is high
chance that there is collision in firmware interface. It means if you
can ack/review that patches then I would take them via arm-soc trees.
Thanks,
Michal
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-02-05 10:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 7:09 [PATCH v2 0/3] Add nvmem driver support for ZynqMP Nava kishore Manne
2019-02-04 7:09 ` [PATCH v2 1/3] firmware: xilinx: Add zynqmp_pm_get_chipid() API Nava kishore Manne
2019-02-03 8:50 ` Srinivas Kandagatla
2019-02-05 10:29 ` Michal Simek [this message]
2019-02-05 10:33 ` Srinivas Kandagatla
2019-02-05 10:36 ` Michal Simek
2019-02-04 7:09 ` [PATCH v2 2/3] dt-bindings: nvmem: Add bindings for ZynqMP nvmem driver Nava kishore Manne
2019-02-04 7:09 ` [PATCH v2 3/3] nvmem: zynqmp: Added zynqmp nvmem firmware driver Nava kishore Manne
2019-02-03 9:38 ` Srinivas Kandagatla
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=f317c341-9706-3a24-6faf-711f2627bcce@xilinx.com \
--to=michal.simek@xilinx.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=rajanv@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@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