From: Philipp Zabel <p.zabel@pengutronix.de>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: Fabio Estevam <fabio.estevam@nxp.com>,
Chris Healy <cphealy@gmail.com>,
Lucas Stach <l.stach@pengutronix.de>,
Leonard Crestez <leonard.crestez@nxp.com>,
"A.s. Dong" <aisheng.dong@nxp.com>,
Richard Zhu <hongxing.zhu@nxp.com>, Rob Herring <robh@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, dl-linux-imx <linux-imx@nxp.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 3/3] reset: imx7: Add support for i.MX8MQ IP block variant
Date: Mon, 28 Jan 2019 11:55:08 +0100 [thread overview]
Message-ID: <1548672908.6421.1.camel@pengutronix.de> (raw)
In-Reply-To: <CAHQ1cqFx3b2fTy8YbpwC0fGJYpO4BLO4FW9q-Z2Np1tVktrKpg@mail.gmail.com>
Hi Andrey,
On Thu, 2019-01-24 at 16:21 -0800, Andrey Smirnov wrote:
> > Thank you, applied all three to reset/next with a small whitespace
> > alignment fix.
> >
>
> Thanks again for applying this stuff. If that's not too much to ask,
> would you mind creating an immutable branch, so I could start sending
> patches that depend on "dt-bindings/reset/imx8mq-reset.h" to i.MX tree
> without waiting for it to trickle down? If not, no worries, I'll wait.
Here is an immutable branch containing just the header/dt-binding patch:
git://git.pengutronix.de/pza/linux reset/imx8mq
regards
Philipp
prev parent reply other threads:[~2019-01-28 10:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 2:10 [PATCH v5 0/3] Reset controller support for i.MX8MQ Andrey Smirnov
2019-01-22 2:10 ` [PATCH v5 1/3] reset: imx7: Add plubming to support multiple IP variants Andrey Smirnov
2019-01-22 2:10 ` [PATCH v5 2/3] dt-bindings: reset: imx7: Document usage on i.MX8MQ SoCs Andrey Smirnov
2019-01-22 2:10 ` [PATCH v5 3/3] reset: imx7: Add support for i.MX8MQ IP block variant Andrey Smirnov
2019-01-23 10:49 ` Philipp Zabel
2019-01-25 0:21 ` Andrey Smirnov
2019-01-28 10:55 ` Philipp Zabel [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=1548672908.6421.1.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=aisheng.dong@nxp.com \
--cc=andrew.smirnov@gmail.com \
--cc=cphealy@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=hongxing.zhu@nxp.com \
--cc=l.stach@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=robh@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;
as well as URLs for NNTP newsgroup(s).