From: Thierry Reding <thierry.reding@avionic-design.de>
To: Jay Agarwal <jagarwal@nvidia.com>
Cc: Stephen Warren <swarren@nvidia.com>,
Juha Tukkinen <jtukkinen@nvidia.com>,
Krishna Thota <kthota@nvidia.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: PCIe code Upstream
Date: Fri, 22 Mar 2013 13:33:59 +0100 [thread overview]
Message-ID: <20130322123359.GA13174@avionic-0098.mockup.avionic-design.de> (raw)
In-Reply-To: <C79B248886DD134989C8FF6B096A91AB91B36FB281@BGMAIL01.nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 356 bytes --]
On Fri, Mar 22, 2013 at 05:59:13PM +0530, Jay Agarwal wrote:
> I don't see can't assign things now on Thierry's latest repo() + my tegra3 support patch, but some reconfiguring things are still there as below:
>
> bridge configuration invalid ([bus 00-00]), reconfiguring
>
>
>
> I am not sure if it's harmless?
That's harmless.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
parent reply other threads:[~2013-03-22 12:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <C79B248886DD134989C8FF6B096A91AB91B36FB281@BGMAIL01.nvidia.com>]
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=20130322123359.GA13174@avionic-0098.mockup.avionic-design.de \
--to=thierry.reding@avionic-design.de \
--cc=jagarwal@nvidia.com \
--cc=jtukkinen@nvidia.com \
--cc=kthota@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@nvidia.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