From: Marek Vasut <marex@denx.de>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Tim Harvey <tharvey@gateworks.com>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Frank Li <lznuaa@gmail.com>, Jingoo Han <jg1.han@samsung.com>,
Mohit KUMAR <Mohit.KUMAR@st.com>,
Pratyush Anand <pratyush.anand@st.com>,
Richard Zhu <r65037@freescale.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Sean Cross <xobs@kosagi.com>, Shawn Guo <shawn.guo@linaro.org>,
Siva Reddy Kallam <siva.kallam@samsung.com>,
Srikanth T Shivanand <ts.srikanth@samsung.com>,
Troy Kisky <troy.kisky@boundarydevices.com>,
Yinghai Lu <yinghai@kernel.org>
Subject: Re: [PATCH] PCI: imx6: increase link startup
Date: Wed, 30 Oct 2013 10:54:50 +0100 [thread overview]
Message-ID: <201310301054.50502.marex@denx.de> (raw)
In-Reply-To: <20131029222036.GB15159@google.com>
Dear Bjorn Helgaas,
> On Tue, Oct 22, 2013 at 10:12:18PM -0700, Tim Harvey wrote:
> > An increase link startup delay is required when certain PCI switches are
> > attached to the root complex. This was tested with a Pericom switch
> > and a PLX switch.
> >
> > From: Marek Vasut <marex@denx.de>
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > Acked-by: Tim Harvey <tharvey@gateworks.com>
>
> I applied this with Shawn's ack to my pci/host-imx6 branch for v3.13,
> thanks!
>
> I assume the intent was that this patch was written by Marek, per the
> "From:" line you added above, so I fixed that in the patch so Marek
> appears as the author. Let me know if this is incorrect.
I'm really glad Tim split this patch while I am being totally unhelpful here on
the PCIe front in last few days. Thank you!
Best regards,
Marek Vasut
prev parent reply other threads:[~2013-10-30 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 5:12 [PATCH] PCI: imx6: increase link startup Tim Harvey
2013-10-23 7:46 ` Shawn Guo
2013-10-29 22:20 ` Bjorn Helgaas
2013-10-30 9:54 ` Marek Vasut [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=201310301054.50502.marex@denx.de \
--to=marex@denx.de \
--cc=Mohit.KUMAR@st.com \
--cc=bhelgaas@google.com \
--cc=jg1.han@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=lznuaa@gmail.com \
--cc=pratyush.anand@st.com \
--cc=r65037@freescale.com \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.org \
--cc=siva.kallam@samsung.com \
--cc=tharvey@gateworks.com \
--cc=troy.kisky@boundarydevices.com \
--cc=ts.srikanth@samsung.com \
--cc=xobs@kosagi.com \
--cc=yinghai@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).