From: Marek Vasut <marex@denx.de>
To: Troy Kisky <troy.kisky@boundarydevices.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
linux-pci@vger.kernel.org, kernel@pengutronix.de,
Richard Zhu <r65037@freescale.com>,
Shawn Guo <shawn.guo@linaro.org>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] PCI: imx6: Fix link_up detection
Date: Thu, 13 Feb 2014 19:41:21 +0100 [thread overview]
Message-ID: <201402131941.21883.marex@denx.de> (raw)
In-Reply-To: <52FD0F1A.4000208@boundarydevices.com>
On Thursday, February 13, 2014 at 07:29:46 PM, Troy Kisky wrote:
> On 2/12/2014 12:36 AM, Marek Vasut wrote:
> > On Wednesday, February 12, 2014 at 08:27:55 AM, Sascha Hauer wrote:
> >
> > +CC Troy Kisky, since I think he submitted something similar some time
> > ago already.
> >
> > Otherwise I agree this happens.
>
> Sorry, I haven't submitted this yet, but was planning to today. Here's
> what would have been sent.
Release early, release often ... ;-)
Best regards,
Marek Vasut
WARNING: multiple messages have this Message-ID (diff)
From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PCI: imx6: Fix link_up detection
Date: Thu, 13 Feb 2014 19:41:21 +0100 [thread overview]
Message-ID: <201402131941.21883.marex@denx.de> (raw)
In-Reply-To: <52FD0F1A.4000208@boundarydevices.com>
On Thursday, February 13, 2014 at 07:29:46 PM, Troy Kisky wrote:
> On 2/12/2014 12:36 AM, Marek Vasut wrote:
> > On Wednesday, February 12, 2014 at 08:27:55 AM, Sascha Hauer wrote:
> >
> > +CC Troy Kisky, since I think he submitted something similar some time
> > ago already.
> >
> > Otherwise I agree this happens.
>
> Sorry, I haven't submitted this yet, but was planning to today. Here's
> what would have been sent.
Release early, release often ... ;-)
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-02-13 21:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 7:27 [PATCH] PCI: imx6: Fix link_up detection Sascha Hauer
2014-02-12 7:27 ` Sascha Hauer
2014-02-12 7:36 ` Marek Vasut
2014-02-12 7:36 ` Marek Vasut
2014-02-13 18:29 ` Troy Kisky
2014-02-13 18:29 ` Troy Kisky
2014-02-13 18:41 ` Marek Vasut [this message]
2014-02-13 18:41 ` Marek Vasut
2014-02-14 6:41 ` Sascha Hauer
2014-02-14 6:41 ` Sascha Hauer
2014-02-14 19:25 ` Troy Kisky
2014-02-14 19:25 ` Troy Kisky
2014-02-18 21:15 ` Bjorn Helgaas
2014-02-18 21:15 ` Bjorn Helgaas
2014-02-19 8:20 ` Sascha Hauer
2014-02-19 8:20 ` Sascha Hauer
2014-02-19 8:27 ` Shawn Guo
2014-02-19 8:27 ` 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=201402131941.21883.marex@denx.de \
--to=marex@denx.de \
--cc=bhelgaas@google.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=r65037@freescale.com \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.org \
--cc=troy.kisky@boundarydevices.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 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.