Re: [git pull, take 2] x86 updates for v2.6.28, phase #9, sparseIRQ?support

[Ingo Molnar]

* Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx> wrote:

> On Friday, October 10, 2008 12:11 pm Yinghai Lu wrote:
> > Ingo Molnar wrote:
> > > * Ingo Molnar <mingo@xxxxxxx> wrote:
> > >> Linus,
> > >>
> > >> Please pull the latest x86-v28-for-linus-phase9 git tree from:
> > >>
> > >> Sparse IRQ support - make NR_IRQS dynamic by turning it into nr_irqs,
> > >> an by creating irq descriptors in a sparse way.
> > >>
> > >> Includes a number of dependent x86 topics: timers/hpet-percpu, IO-APIC
> > >> and local APIC code unification, UV support updates.
> > >>
> > >> Has been cross-built on all architectures we could get crosscompilers
> > >> for:
> > >>
> > >>   http://www.tglx.de/autoqa/index
> > >>
> > >> It should be largely uneventful for sparse-irq unaware, non-x86
> > >> architectures.
> > >
> > > please find updated pull request below. Relative to phase-N-1. Updates
> > > from today in this class of topics:
> > >
> > >   b570868: x86: apic - unify APIC_DIVISOR
> > >
> > > And i removed:
> > >
> > >   eada62c: acpi/x86: introduce __apci_map_table, v4
> > >
> > > [ Cc:-ed Yinghai for that - we can live without that patch (i.e. we at
> > >   most get a leak warning) and can have that via acpi.git, correct? ]
> >
> > yes. we have several patches that even didn't pick up for a while.
> >
> > also please ask Linus to pull pci tree from Jesse before sparseirq.
> >
> > because we need
> > 	PCI: change MSI-x vector to 32bit
> >
> > in pci tree.
> 
> I should have my pull ready soon; I'd like to do some cross compile tests with 
> my latest bits first.  But I think Ingo has a copy of this commit anyway so 
> it may be ok for Linus to pull anyway.

Correct, it's safe to pull it, because irq/sparseirq has this commit:

  9e40236: pci: change msi-x vector to 32bit

it's content-equal with yours so your merge should be painless.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/