From: Sinan Akman <sinan@writeme.com>
To: Tim Harvey <tharvey@gateworks.com>
Cc: "Zhu Richard-R65037" <r65037@freescale.com>,
"Marek Vašut" <marex@denx.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Pratyush Anand" <pratyush.anand@st.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Jingoo Han" <jg1.han@samsung.com>,
"Troy Kisky" <troy.kisky@boundarydevices.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Sean Cross" <xobs@kosagi.com>,
"Shawn Guo" <shawn.guo@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v6 3/3] PCI: imx6: Add support for i.MX6 PCIe controller
Date: Tue, 05 Nov 2013 12:35:26 -0500 [thread overview]
Message-ID: <52792C5E.6030008@writeme.com> (raw)
In-Reply-To: <CAJ+vNU2ifxfprYsgcQs+Kkgu37+diXHJS6DEqs4d51+U3F4sLQ@mail.gmail.com>
On 10/18/2013 11:34 AM, Tim Harvey wrote:
> On Fri, Oct 18, 2013 at 12:45 AM, Zhu Richard-R65037
> [...]
> How about with the upstream driver? I have 'my own driver' as well
> (based on Freescale's BSP) which works, but I'm very interested in
> getting this upstream driver to work so we don't have to keep
> maintaining our own drivers. Can you please test with this upstream
> driver?
Tim, Sean what is the status of this patch ? Is it part of any tree
already ? I'd like to test few things.
Thanks
Sinan Akman
next prev parent reply other threads:[~2013-11-05 17:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 8:20 [PATCH v6 0/3] Add PCIe support for i.MX6q Sean Cross
2013-09-16 8:20 ` [PATCH v6 2/3] ARM: imx6q: Add PCIe bits to GPR syscon definition Sean Cross
[not found] ` <1379319655-20210-1-git-send-email-xobs-nXMMniAx+RbQT0dZR+AlfA@public.gmane.org>
2013-09-16 8:20 ` [PATCH v6 1/3] ARM: imx: Add LVDS general-purpose clocks to i.MX6Q Sean Cross
2013-09-16 8:20 ` [PATCH v6 3/3] PCI: imx6: Add support for i.MX6 PCIe controller Sean Cross
2013-09-16 9:25 ` Sascha Hauer
2013-09-25 16:05 ` Frank Li
[not found] ` <1379319655-20210-4-git-send-email-xobs-nXMMniAx+RbQT0dZR+AlfA@public.gmane.org>
2013-09-26 5:54 ` Tim Harvey
[not found] ` <CAJ+vNU32oMZq=jrSCpk_ZjYc08kRBAqhOS8uYfor28gY8WGhnw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-27 1:38 ` Zhu Richard-R65037
[not found] ` <0E83723C55F66F43A6041464FE31119D3F7E6A-RL0Hj/+nBVDAtPZc1oz0FK4g8xLGJsHaLnY5E4hWTkheoWH0uzbU5w@public.gmane.org>
2013-09-27 2:19 ` Shawn Guo
[not found] ` <20130927021925.GF25146-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2013-09-27 3:40 ` Jingoo Han
[not found] ` <017e01cebb33$44fa65b0$ceef3110$%han-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-09-27 3:54 ` Sean Cross
2013-09-27 3:52 ` Tim Harvey
2013-10-18 5:32 ` Tim Harvey
2013-10-18 6:34 ` Zhu Richard-R65037
2013-10-18 7:27 ` Tim Harvey
2013-10-18 7:45 ` Zhu Richard-R65037
2013-10-18 15:34 ` Tim Harvey
2013-11-05 17:35 ` Sinan Akman [this message]
2013-11-05 20:28 ` Bjorn Helgaas
2013-09-16 9:11 ` [PATCH v6 0/3] Add PCIe support for i.MX6q Shawn Guo
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=52792C5E.6030008@writeme.com \
--to=sinan@writeme.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=jg1.han@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=marex@denx.de \
--cc=pratyush.anand@st.com \
--cc=r65037@freescale.com \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.org \
--cc=tharvey@gateworks.com \
--cc=troy.kisky@boundarydevices.com \
--cc=xobs@kosagi.com \
/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).