Re: tip: patches in git for irq and numa

From: Ingo Molnar
Date: Mon May 18 2009 - 09:58:25 EST



* Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote:

> On Mon, 2009-05-18 at 09:29 +0200, Ingo Molnar wrote:
> > * Yinghai Lu <yinghai@xxxxxxxxxx> wrote:
> >
> > > irq related:
> > > git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-2.6-yinghai.git irq
> > > need to on top of tip/irq/numa
> >
> > ok, these were nicely structured. the pci_routeirq patch had a build
> > bug for !CONFIG_PCI.
> >
> > ( I added an #ifdef for now, it might make sense to send a clean-up
> > patch in the next merge window (not now) to factor out a
> > pci_routeirq_enable() method that does all this cleanly. )
> >
> > Also, please add appropriate Cc: lines to the commit logs in the
> > future, beyond the LKML-Reference tgs.
> >
> > > for memoryless node support:
> > > git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-2.6-yinghai.git numa
> > > and it is on top of tip/master
> >
> > small note: you could have based these on x86/mm btw. - that's where
> > these patches go, typically.
> >
> > regarding subject lines:
> >
> > d03a6a4: mm: clear N_HIGH_MEMORY map before se set it again -v2
> > 02ce039: x86: fix system without memory on node0 -v2
> > 8c1aec8: x86: fix node_possible_map logic -v2
> > 44a633c: x86: remove MEMORY_HOTPLUG_RESERVE related code -v2
> >
> > please never put '-v2' type of tags into the title of commits. In
> > the title of patches they can be put here:
> >
> > [PATCH, v2] x86: fix system without memory on node0
> >
> > that saves maintainers a bit of typing work.
> >
> > Also, you included:
> >
> > d03a6a4: mm: clear N_HIGH_MEMORY map before se set it again -v2
> >
> > with no Acks from MM folks yet. So i skipped that one and will
> > follow up about it.
>
> The below seems to wreck my opteron, ata1 interrupts fail to get
> through.

thanks Peter for bisecting this, i've excluded irq/numa from
tip:master again.

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/