From: Rusty Russell <rusty@rustcorp.com.au>
To: Mike Travis <travis@sgi.com>
Cc: Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] x86: fix assign_irq_vector boot up problem
Date: Fri, 12 Dec 2008 18:57:55 +1030 [thread overview]
Message-ID: <200812121857.55929.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20081211112806.740820000@polaris-admin.engr.sgi.com>
On Thursday 11 December 2008 21:58:07 Mike Travis wrote:
> Impact: fix boot up problem.
>
> Fix a problem encountered with the Intel SATA-AHCI disk driver
> right at system startup. Cpumask_intersects really needs to be
> a 3-way intersect, and since we need a cpumask_var_t later on,
> then just use it for the 3-way intersect as well.
This one looks fine.
My plan was for Ingo to pull that for-ingo tree into his cpus4096 tree
and take the x86 patches from there. But he hasn't so maybe I should
take this chance to fold that patch in?
Thanks,
Rusty.
next prev parent reply other threads:[~2008-12-12 8:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 11:28 [PATCH 0/4] cpumask: fixups and additions Mike Travis
2008-12-11 11:28 ` [PATCH 1/4] x86: fix assign_irq_vector boot up problem Mike Travis
2008-12-12 8:27 ` Rusty Russell [this message]
2008-12-12 9:20 ` Ingo Molnar
2008-12-12 18:10 ` Mike Travis
2008-12-12 19:06 ` Mike Travis
2008-12-11 11:28 ` [PATCH 2/4] x86: fix cpu_mask_to_apicid_and to include cpu_online_mask Mike Travis
2008-12-12 11:06 ` Rusty Russell
2008-12-12 16:37 ` Mike Travis
2008-12-13 12:03 ` Rusty Russell
2008-12-11 11:28 ` [PATCH 3/4] cpumask: use maxcpus=NUM to extend the cpu limit as well as restrict the limit Mike Travis
2008-12-11 13:41 ` Heiko Carstens
2008-12-11 18:19 ` Mike Travis
2008-12-12 10:03 ` Heiko Carstens
2008-12-12 11:41 ` Rusty Russell
2008-12-12 15:38 ` Mike Travis
2008-12-11 11:28 ` [PATCH 4/4] cpumask: add sysfs displays for configured and disabled cpu maps Mike Travis
2008-12-12 11:44 ` Rusty Russell
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=200812121857.55929.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.