From: Shawn Guo <shawnguo@kernel.org>
To: peng.fan@nxp.com
Cc: s.hauer@pengutronix.de, aisheng.dong@nxp.com, festevam@gmail.com,
qiangqing.zhang@nxp.com, linux@rempel-privat.de,
franck.lenormand@nxp.com, linux-arm-kernel@lists.infradead.org,
kernel@pengutronix.de, leonard.crestez@nxp.com,
daniel.baluta@nxp.com, linux-kernel@vger.kernel.org,
linux-imx@nxp.com
Subject: Re: [PATCH V3 0/3] firmware: imx: fix/update cm4 and add resource check
Date: Tue, 23 Jun 2020 15:38:26 +0800 [thread overview]
Message-ID: <20200623073825.GW30139@dragon> (raw)
In-Reply-To: <1591322372-3793-1-git-send-email-peng.fan@nxp.com>
On Fri, Jun 05, 2020 at 09:59:29AM +0800, peng.fan@nxp.com wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> V3:
> Fix comments
> Add R-b tag
>
> V2:
> Add R-b tag
> Drop patch 3/4 from V1
> Add comments and update Copyright for patch 2/3
> keep code consistency in Patch 3/3
>
> V1:
> https://patchwork.kernel.org/cover/11505045/
>
> Fix cm40 power domain, update to add more cm4 resources
> Add resource owner check, to not register if not owned by Linux.
>
> Peng Fan (3):
> firmware: imx: scu-pd: fix cm40 power domain
> firmware: imx: add resource management api
> firmware: imx: scu-pd: add more cm4 resources
Applied all, thanks.
prev parent reply other threads:[~2020-06-23 7:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 1:59 [PATCH V3 0/3] firmware: imx: fix/update cm4 and add resource check peng.fan
2020-06-05 1:59 ` peng.fan
2020-06-05 1:59 ` [PATCH V3 1/3] firmware: imx: scu-pd: fix cm40 power domain peng.fan
2020-06-05 1:59 ` peng.fan
2020-06-05 1:59 ` [PATCH V3 2/3] firmware: imx: add resource management api peng.fan
2020-06-05 1:59 ` peng.fan
2020-06-05 1:59 ` [PATCH V3 3/3] firmware: imx: scu-pd: add more cm4 resources peng.fan
2020-06-05 1:59 ` peng.fan
2020-06-23 7:38 ` Shawn Guo [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=20200623073825.GW30139@dragon \
--to=shawnguo@kernel.org \
--cc=aisheng.dong@nxp.com \
--cc=daniel.baluta@nxp.com \
--cc=festevam@gmail.com \
--cc=franck.lenormand@nxp.com \
--cc=kernel@pengutronix.de \
--cc=leonard.crestez@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=peng.fan@nxp.com \
--cc=qiangqing.zhang@nxp.com \
--cc=s.hauer@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.