From: Jacky Bai <ping.bai@nxp.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Aisheng Dong <aisheng.dong@nxp.com>,
"festevam@gmail.com" <festevam@gmail.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>
Subject: RE: [PATCH v2 2/2] pinctrl: freescale: Add imx8mm pinctrl driver support
Date: Tue, 29 Jan 2019 02:06:43 +0000 [thread overview]
Message-ID: <VI1PR0402MB351949F8A607FFEA7CF6394087970@VI1PR0402MB3519.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <CACRpkdZwEKew1SLAkCEr-yxUt_m6Hzh6COVjCfM703ufcdHXiQ@mail.gmail.com>
> Subject: Re: [PATCH v2 2/2] pinctrl: freescale: Add imx8mm pinctrl driver
> support
>
> On Tue, Jan 22, 2019 at 11:17 AM Jacky Bai <ping.bai@nxp.com> wrote:
>
> > From: Bai Ping <ping.bai@nxp.com>
> >
> > Add the pinctrl driver support for i.MX8MM.
> >
> > Signed-off-by: Bai Ping <ping.bai@nxp.com>
> > Acked-by: Aisheng Dong <aisheng.dong@nxp.com>
> > ---
> > change v1->v2:
> > - remove unnecessary header file include.
>
> This doesn't apply on the current pinctrl devel branch, I suppose it's the
> imx8qm patch that disturbs it.
> Can you check and possibly respin on my branch?
Yes, it is disturbed by 8qm patch, I will send out V3.
BR
>
> Yours,
> Linus Walleij
next prev parent reply other threads:[~2019-01-29 2:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 10:17 [PATCH v2 1/2] dt-bindings: imx: Add pinctrl binding doc for imx8mm Jacky Bai
2019-01-22 10:17 ` [PATCH v2 2/2] pinctrl: freescale: Add imx8mm pinctrl driver support Jacky Bai
2019-01-28 13:17 ` Linus Walleij
2019-01-29 2:06 ` Jacky Bai [this message]
2019-01-28 13:11 ` [PATCH v2 1/2] dt-bindings: imx: Add pinctrl binding doc for imx8mm Linus Walleij
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=VI1PR0402MB351949F8A607FFEA7CF6394087970@VI1PR0402MB3519.eurprd04.prod.outlook.com \
--to=ping.bai@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@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 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.