From: Linus Torvalds <torvalds@linux-foundation.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [GIT PULL] percpu, cpumask, x86 updates for v2.6.30
Date: Sat, 28 Mar 2009 20:53:21 +0000 [thread overview]
Message-ID: <alpine.LFD.2.00.0903281341100.3994@localhost.localdomain> (raw)
On Sat, 28 Mar 2009, Ingo Molnar wrote:
>
> Below is this tree merged against latest -git, resolving two new
> conflicts. I forgot to mention that the percpu/MM changes are fine
> by Andrew too.
Ingo, I think you ia64 stuff was broken. It used "vector" to get to the
irq descriptor. Which is not the same as an "irq" at all.
The reason I noticed is that it clashed with the ia64 pull, which had
fixed this up.
I tried to fix it all up. But I'm just about the last person in the
universe who wants to compile ia64, so I have not tested, or even been
able to see that it compiles. Somebody should double-check it.
Linus
next reply other threads:[~2009-03-28 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-28 20:53 Linus Torvalds [this message]
2009-03-28 20:59 ` [GIT PULL] percpu, cpumask, x86 updates for v2.6.30 Ingo Molnar
2009-03-28 21:24 ` Ingo Molnar
2009-03-30 15:52 ` Luck, Tony
2009-03-31 10:17 ` Ingo Molnar
2009-03-31 18:39 ` Luck, Tony
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=alpine.LFD.2.00.0903281341100.3994@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=linux-ia64@vger.kernel.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