From: Christoph Fritz <chf.fritz@googlemail.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Lee Jones <lee.jones@linaro.org>,
Lucas Stach <l.stach@pengutronix.de>,
Richard Zhu <hongxing.zhu@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
Fabio Estevam <fabio.estevam@nxp.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 0/2] Add PCIe driver support for imx6sx
Date: Wed, 09 Mar 2016 16:39:57 +0100 [thread overview]
Message-ID: <1457537997.17531.3.camel@googlemail.com> (raw)
In-Reply-To: <1457338819.1904.4.camel@googlemail.com>
On Mon, 2016-03-07 at 09:20 +0100, Christoph Fritz wrote:
> On Thu, 2016-03-03 at 01:48 +0000, Richard Zhu wrote:
> > > -----Original Message-----
> > > From: Christoph Fritz [mailto:chf.fritz@googlemail.com]
> > > Sent: Thursday, February 25, 2016 10:48 PM
> > > To: Richard Zhu; Lucas Stach; Shawn Guo; Fabio Estevam; Bjorn Helgaas; Lee
> > > Jones
> > > Cc: linux-pci@vger.kernel.org; linux-arm-kernel@lists.infradead.org
> > > Subject: [PATCH v3 0/2] Add PCIe driver support for imx6sx
> > >
> > > v3:
> > > * adapt devicetree bindings documentation fsl,imx6q-pcie.txt
> > > v2:
> > > * leave out regulator handling from driver, will be done later
> > > in PM subsystem
> > > * use BIT() macro for MFD
> > >
> > > Christoph Fritz (2):
> > > MFD: imx6sx: Add PCIe register definitions for iomuxc gpr
> > > PCI: imx6: add initial imx6sx support
> > >
> > > .../devicetree/bindings/pci/fsl,imx6q-pcie.txt | 6 +-
> > > drivers/pci/host/pci-imx6.c | 130 ++++++++++++++-------
> > > include/linux/mfd/syscon/imx6q-iomuxc-gpr.h | 5 +
> > > 3 files changed, 101 insertions(+), 40 deletions(-)
> > >
> > > --
> > > 2.1.4
> >
> > [Zhu hongxing] Acked-by: Richard Zhu <Richard.Zhu@freescale.com>
> > Richard
> > Best Regards
>
> @Bjorn: I suppose the PCI patch need to go through your tree. Would you
> pick up this patch?
*ping*
Do you want me to rebase my patch to your pci/host-imx6 branch?
Thanks
-- Christoph
next prev parent reply other threads:[~2016-03-09 15:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 14:47 [PATCH v3 0/2] Add PCIe driver support for imx6sx Christoph Fritz
2016-02-25 14:47 ` [PATCH v3 1/2] MFD: imx6sx: Add PCIe register definitions for iomuxc gpr Christoph Fritz
2016-03-08 4:32 ` Lee Jones
2016-02-25 14:47 ` [PATCH v3 2/2] PCI: imx6: add initial imx6sx support Christoph Fritz
2016-03-11 17:58 ` Bjorn Helgaas
2016-03-13 23:26 ` Christoph Fritz
2016-03-13 23:30 ` PCI: imx6: Factor out ref clock enable Christoph Fritz
2016-03-20 7:29 ` Christoph Fritz
2016-04-05 21:56 ` Bjorn Helgaas
2016-03-13 23:31 ` [PATCH v4] PCI: imx6: Add initial imx6sx support Christoph Fritz
2016-03-20 7:30 ` Christoph Fritz
2016-04-05 21:56 ` Bjorn Helgaas
2016-03-03 1:41 ` [PATCH v3 0/2] Add PCIe driver support for imx6sx Christoph Fritz
2016-03-03 1:46 ` Richard Zhu
2016-03-03 1:48 ` Richard Zhu
2016-03-07 8:20 ` Christoph Fritz
2016-03-09 15:39 ` Christoph Fritz [this message]
2016-03-09 15:53 ` Lucas Stach
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=1457537997.17531.3.camel@googlemail.com \
--to=chf.fritz@googlemail.com \
--cc=fabio.estevam@nxp.com \
--cc=helgaas@kernel.org \
--cc=hongxing.zhu@nxp.com \
--cc=l.stach@pengutronix.de \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.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 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).