On Mon, Aug 12, 2013 at 06:16:13PM +0200, Thierry Reding wrote:
> 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.
Yes, Thomas fixed it by properly implementing weak across the archs. I
got wrapped around the axle yesterday, so I'm working on it today.
Should have a stable branch for you in an hour or so.
thx,
Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
