From: Thierry Reding <thierry.reding@avionic-design.de>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Stephen Warren <swarren@nvidia.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"Olof Johansson (olof@lixom.net)" <olof@lixom.net>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-pci@vger.kernel.org
Subject: Re: PCIe device tree support
Date: Fri, 24 Feb 2012 07:59:21 +0100 [thread overview]
Message-ID: <20120224065921.GA28932@avionic-0098.mockup.avionic-design.de> (raw)
In-Reply-To: <CAErSpo7wSB-uCjV4YeA-fUOHPtugn4ASXScN3MndVybfkk8mOw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 212 bytes --]
* Bjorn Helgaas wrote:
> I agree that if the code isn't shared at all, there's no point in
> putting it in a generic place like drivers/pci/.
Alright, I'll keep the driver in arch/arm/mach-tegra/ then.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-02-24 6:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 19:18 PCIe device tree support Thierry Reding
[not found] ` <20120220191804.GA14499-RM9K5IK7kjIyiCvfTdI0JKcOhU4Rzj621B7CTYaBSLdn68oJJulU0Q@public.gmane.org>
2012-02-21 17:15 ` Stephen Warren
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF17BD8BC302-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2012-02-22 8:24 ` Thierry Reding
[not found] ` <20120222082449.GA15157-RM9K5IK7kjIyiCvfTdI0JKcOhU4Rzj621B7CTYaBSLdn68oJJulU0Q@public.gmane.org>
2012-02-22 16:01 ` Bjorn Helgaas
[not found] ` <CAErSpo4TfpGmx+HZ1ZnZwj3ZP_cQMCzkMT+6JK6ztYp2zWJcxw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-23 6:03 ` Thierry Reding
2012-02-23 16:16 ` Jesse Barnes
2012-02-23 16:17 ` Olof Johansson
2012-02-23 17:49 ` Bjorn Helgaas
2012-02-24 6:59 ` Thierry Reding [this message]
[not found] ` <20120224065921.GA28932-RM9K5IK7kjIQXX3q8xo1gnVAuStQJXxyR5q1nwbD4aMs9pC9oP6+/A@public.gmane.org>
2012-02-24 17:16 ` Pratyush Anand
2012-02-24 17:25 ` Bjorn Helgaas
[not found] ` <CAHM4w1k1_Yp56tpfPqDxT1WHQWRB5xe_Zs-BEj+n5rVmuyAJiw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-24 17:27 ` Jesse Barnes
[not found] ` <CAErSpo7wSB-uCjV4YeA-fUOHPtugn4ASXScN3MndVybfkk8mOw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-28 18:17 ` Bjorn Helgaas
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=20120224065921.GA28932@avionic-0098.mockup.avionic-design.de \
--to=thierry.reding@avionic-design.de \
--cc=bhelgaas@google.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=olof@lixom.net \
--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