RE: [GIT PULL] percpu, cpumask, x86 updates for v2.6.30
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: Ingo Molnar <mingo@xxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, Mike Travis <travis@xxxxxxx>, Jes Sorensen <jes@xxxxxxx>
- Subject: RE: [GIT PULL] percpu, cpumask, x86 updates for v2.6.30
- From: "Luck, Tony" <tony.luck@xxxxxxxxx>
- Date: Mon, 30 Mar 2009 08:52:44 -0700
- Accept-language: en-US
- Acceptlanguage: en-US
- Cc: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, "linux-ia64@xxxxxxxxxxxxxxx" <linux-ia64@xxxxxxxxxxxxxxx>
- In-reply-to: <20090328212434.GA11629@xxxxxxx>
- List-id: <linux-ia64.vger.kernel.org>
- References: <20090326214152.GA5472@xxxxxxx> <20090328033545.GA8400@xxxxxxx> <alpine.LFD.2.00.0903281341100.3994@xxxxxxxxxxxxxxxxxxxxx> <20090328205928.GA3955@xxxxxxx> <20090328212434.GA11629@xxxxxxx>
- Thread-index: Acmv65587U8+aObrRz+M7oYdhuv88gBY0gMQ
- Thread-topic: [GIT PULL] percpu, cpumask, x86 updates for v2.6.30
Ingo,
Thanks for looking at this ... I'll try to do some sanity checks
on the IRQ stats to make sure that they make sense.
I do question this part:
> It didnt crash though: this commit has been in linux-next for 2
> months.
I've been building linux-next for ia64 at least a couple of
times a week ... and I didn't see the build error from these
changes there. First time I saw it was when it showed up in Linus'
tree. Can you check that all of your trees are in the list
to pull into linux-next? Perhaps this one got missed?
-Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Kernel]
[Sparc Linux]
[DCCP]
[Linux ARM]
[Yosemite News]
[Linux SCSI]
[Linux x86_64]
[Linux for Ham Radio]
