From: Christoph Fritz <chf.fritz@googlemail.com>
To: Richard Zhu <hongxing.zhu@nxp.com>, Lucas Stach <l.stach@pengutronix.de>
Cc: Fabio Estevam <festevam@gmail.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Lee Jones <lee.jones@linaro.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Fabio Estevam <fabio.estevam@nxp.com>
Subject: Re: [PATCH v2 2/2] PCI: imx6: add initial imx6sx support
Date: Mon, 22 Feb 2016 10:19:51 +0100 [thread overview]
Message-ID: <1456132791.1860.3.camel@googlemail.com> (raw)
In-Reply-To: <1456101636.2176.4.camel@googlemail.com>
On Mon, 2016-02-22 at 01:40 +0100, Christoph Fritz wrote:
> On Sat, 2016-02-20 at 17:37 -0200, Fabio Estevam wrote:
> > On Thu, Feb 18, 2016 at 9:59 AM, Christoph Fritz
> > <chf.fritz@googlemail.com> wrote:
> >
> > > static const struct of_device_id imx6_pcie_of_match[] = {
> > > { .compatible = "fsl,imx6q-pcie", },
> > > + { .compatible = "fsl,imx6sx-pcie", },
> >
> > Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.txt needs to be
> > updated to include this new compatible string.
>
> Thanks, I'll wait a bit for other possible comments and will then send a
> v3 patchset which updates the documentation too.
>
@MAINTAINERS (Lucas or Richard):
Do you want the documentation changes as a separate patch?
prev parent reply other threads:[~2016-02-22 9:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 11:59 [PATCH v2 0/2] Add PCIe driver support for imx6sx Christoph Fritz
2016-02-18 11:59 ` [PATCH v2 1/2] MFD: imx6sx: Add PCIe register definitions for iomuxc gpr Christoph Fritz
2016-02-18 11:59 ` [PATCH v2 2/2] PCI: imx6: add initial imx6sx support Christoph Fritz
2016-02-20 19:37 ` Fabio Estevam
2016-02-22 0:40 ` Christoph Fritz
2016-02-22 9:19 ` Christoph Fritz [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=1456132791.1860.3.camel@googlemail.com \
--to=chf.fritz@googlemail.com \
--cc=bhelgaas@google.com \
--cc=fabio.estevam@nxp.com \
--cc=festevam@gmail.com \
--cc=hongxing.zhu@nxp.com \
--cc=l.stach@pengutronix.de \
--cc=lee.jones@linaro.org \
--cc=linux-pci@vger.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.