public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: linux-ia64@vger.kernel.org
Subject: Re: [GIT PULL] percpu, cpumask, x86 updates for v2.6.30
Date: Tue, 31 Mar 2009 10:17:03 +0000	[thread overview]
Message-ID: <20090331101703.GA20904@elte.hu> (raw)
In-Reply-To: <alpine.LFD.2.00.0903281341100.3994@localhost.localdomain>


* Luck, Tony <tony.luck@intel.com> wrote:

> 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?

They are and were all there. There was no build problem here AFAICS 
- just a conflict which Linus saw and resolved [correctly AFAICS].

( And i build ia64 daily, against our full tree, so i'd have noticed
  any build breakage. )

If there was something here that shouldnt have happened then let me 
know and i'll trace back exactly how it happened and will prevent it 
in the future.

	Ingo

  parent reply	other threads:[~2009-03-31 10:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-28 20:53 [GIT PULL] percpu, cpumask, x86 updates for v2.6.30 Linus Torvalds
2009-03-28 20:59 ` Ingo Molnar
2009-03-28 21:24 ` Ingo Molnar
2009-03-30 15:52 ` Luck, Tony
2009-03-31 10:17 ` Ingo Molnar [this message]
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=20090331101703.GA20904@elte.hu \
    --to=mingo@elte.hu \
    --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