linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	linux-tegra@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v6 00/14] Rewrite Tegra PCIe driver
Date: Mon, 12 Aug 2013 18:16:13 +0200	[thread overview]
Message-ID: <20130812161612.GA8282@ulmo> (raw)
In-Reply-To: <20130809150831.GF25111@titan.lakedaemon.net>

[-- Attachment #1: Type: text/plain, Size: 1648 bytes --]

On Fri, Aug 09, 2013 at 11:08:31AM -0400, Jason Cooper wrote:
> On Fri, Aug 09, 2013 at 04:49:18PM +0200, Thierry Reding wrote:
> > Hi Stephen,
> > 
> > This is the latest version of the Tegra PCIe driver patch series. I've
> > dropped the PCI xclk clamping code as discussed and successfully tested
> > on Beaver. The patches that touch the PCI subsystem have Bjorn's
> > Acked-by and I've tested this on top of next-20130809, which has Jason's
> > common branch. Once he's comfortable with making the branch stable you
> > should be able to merge that branch and apply these patches on top.
> 
> Just an FYI, I'm mostly happy with what we have now, except that I'd
> like to confirm that the build failure Randy discovered isn't caused by
> us:
> 
> Randy wrote some time later:
> > On 08/08/13 00:08, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Changes since 20130807:
> > >
> > 
> > on i386 and x86_64:
> > when CONFIG_PCI_MSI is not enabled:
> > 
> > There are many of these errors:
> > include/linux/msi.h:65:6: error: expected identifier or '(' before 'void'
> > include/linux/msi.h:65:6: error: expected ')' before numeric constant
> > 
> > because arch/x86/include/asm/pci.h defines:
> > #define default_teardown_msi_irqs NULL
> 
> I'm having a helluva time reproducing it :(
> 
> The next run of linux-next isn't until Sunday evening (AUS Monday
> morning), so we have some time to figure it out.
> 
> Also, I've renamed the branch mvebu/msi_pci to more accurately describe
> the changes it contains.

Has there been any progress on this? If not I'll take a look at it
tomorrow.

Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-08-12 16:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 14:49 [PATCH v6 00/14] Rewrite Tegra PCIe driver Thierry Reding
2013-08-09 14:49 ` [PATCH v6 01/14] PCI: tegra: Move PCIe driver to drivers/pci/host Thierry Reding
2013-08-09 14:49 ` [PATCH v6 02/14] ARM: tegra: tamonten: Add PCIe support Thierry Reding
2013-08-09 14:49 ` [PATCH v6 03/14] ARM: tegra: tec: " Thierry Reding
2013-08-09 14:49 ` [PATCH v6 04/14] ARM: tegra: harmony: Initialize PCIe from DT Thierry Reding
2013-08-09 14:49 ` [PATCH v6 05/14] ARM: tegra: trimslice: " Thierry Reding
2013-08-09 14:49 ` [PATCH v6 06/14] PCI: tegra: Add Tegra 30 PCIe support Thierry Reding
2013-08-09 14:49 ` [PATCH v6 07/14] PCI: tegra: set up PADS_REFCLK_CFG1 Thierry Reding
2013-08-09 14:49 ` [PATCH v6 08/14] ARM: tegra: Add Tegra30 PCIe support Thierry Reding
2013-08-09 14:49 ` [PATCH v6 09/14] ARM: tegra: Enable PCIe controller on Cardhu Thierry Reding
2013-08-09 14:49 ` [PATCH v6 10/14] ARM: tegra: Enable PCIe controller on Beaver Thierry Reding
2013-08-09 14:49 ` [PATCH v6 11/14] ARM: tegra: Fix Beaver's PCIe lane configuration Thierry Reding
2013-08-09 14:49 ` [PATCH v6 12/14] ARM: tegra: Update default configuration (PCIe) Thierry Reding
2013-08-09 14:49 ` [PATCH v6 13/14] ARM: dts: tegra: Increase prefetchable PCI memory space Thierry Reding
2013-08-09 14:49 ` [PATCH v6 14/14] MAINTAINERS: Add myself as Tegra PCIe maintainer Thierry Reding
2013-08-09 14:56   ` Bjorn Helgaas
2013-08-09 15:08 ` [PATCH v6 00/14] Rewrite Tegra PCIe driver Jason Cooper
2013-08-12 16:16   ` Thierry Reding [this message]
2013-08-12 16:22     ` Jason Cooper
2013-08-12 21:19 ` Stephen Warren

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=20130812161612.GA8282@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=swarren@wwwdotorg.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).