From: "Chen, Gong" <gong.chen@linux.intel.com>
To: Prarit Bhargava <prarit@redhat.com>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
Michel Lespinasse <walken@google.com>,
Seiji Aguchi <seiji.aguchi@hds.com>,
Yang Zhang <yang.z.zhang@Intel.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Janet Morgan <janet.morgan@Intel.com>,
Tony Luck <tony.luck@Intel.com>, Ruiv Wang <ruiv.wang@gmail.com>,
Yinghai Lu <yinghai@kernel.org>,
"H. Peter Anvin" <hpa@linux.intel.com>
Subject: Re: [PATCH] x86, make check_irq_vectors_for_cpu_disable() aware of numa node irqs
Date: Sun, 2 Mar 2014 22:32:50 -0500 [thread overview]
Message-ID: <20140303033250.GA22677@gchen.bj.intel.com> (raw)
In-Reply-To: <1393337061-1315-1-git-send-email-prarit@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 658 bytes --]
On Tue, Feb 25, 2014 at 09:04:21AM -0500, Prarit Bhargava wrote:
> This patch explicitly depends on Yinghai's patch, [PATCH v3] x86, irq: get
> correct available vectors for cpu disable, which was last posted here:
>
> http://marc.info/?l=linux-kernel&m=139094603622814&w=2
>
> and is not yet in any tree AFAICT.
>
> P.
>
Sounds reasonable to me. Just a nitpick.
Acked-by: Gong Chen <gong.chen@linux.intel.com>
[...]
> + if (cpumask_empty(&affinity_new)) {
> + pr_warn("CPU %d disable failed: IRQ %u has no availble CPUS to transition IRQ.\n",
These words looks not fluent to native speaker. (but I'm not native
speaker, too ;-))
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-03-03 3:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 14:04 [PATCH] x86, make check_irq_vectors_for_cpu_disable() aware of numa node irqs Prarit Bhargava
2014-03-03 3:32 ` Chen, Gong [this message]
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=20140303033250.GA22677@gchen.bj.intel.com \
--to=gong.chen@linux.intel.com \
--cc=ak@linux.intel.com \
--cc=hpa@linux.intel.com \
--cc=janet.morgan@Intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=prarit@redhat.com \
--cc=ruiv.wang@gmail.com \
--cc=seiji.aguchi@hds.com \
--cc=tony.luck@Intel.com \
--cc=walken@google.com \
--cc=yang.z.zhang@Intel.com \
--cc=yinghai@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