From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-tip-commits@vger.kernel.org"
<linux-tip-commits@vger.kernel.org>
Subject: Re: [tip:irq/core] genirq: Set initial affinity in irq_set_affinity_hint()
Date: Wed, 28 Jan 2015 11:58:00 -0800 [thread overview]
Message-ID: <20150128115800.000065fc@unknown> (raw)
In-Reply-To: <CAE9FiQWiUF4Rs4+f3q3nww1iNNbVSAZcZX5akYyQa=3Avf1fqg@mail.gmail.com>
On Tue, 27 Jan 2015 22:36:23 -0800
Yinghai Lu <yinghai@kernel.org> wrote:
> On Fri, Jan 23, 2015 at 2:42 AM, tip-bot for Jesse Brandeburg
> <tipbot@zytor.com> wrote:
> > Commit-ID: e2e64a932556cdfae455497dbe94a8db151fc9fa
> > Gitweb: http://git.kernel.org/tip/e2e64a932556cdfae455497dbe94a8db151fc9fa
> > Author: Jesse Brandeburg <jesse.brandeburg@intel.com>
> > AuthorDate: Thu, 18 Dec 2014 17:22:06 -0800
> > Committer: Thomas Gleixner <tglx@linutronix.de>
> > CommitDate: Fri, 23 Jan 2015 11:38:25 +0100
> >
> > genirq: Set initial affinity in irq_set_affinity_hint()
> there are lots of irq_set_affinity_hint(irq, NULL);
>
> git grep -A 1 irq_set_affinity_hint | grep NULL | wc -l
> 26
>
> You may need to add check ...in irq_set_affinity_hint()
Patch posted to fix the issue (added a null check)
next prev parent reply other threads:[~2015-01-28 20:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 1:22 [PATCH] genirq: set initial affinity when hinting Jesse Brandeburg
2014-12-19 19:53 ` Jesse Brandeburg
2015-01-23 10:42 ` [tip:irq/core] genirq: Set initial affinity in irq_set_affinity_hint() tip-bot for Jesse Brandeburg
2015-01-28 6:36 ` Yinghai Lu
2015-01-28 16:43 ` Jesse Brandeburg
2015-01-28 19:58 ` Jesse Brandeburg [this message]
2015-02-09 8:22 ` Ingo Molnar
2015-02-09 17:48 ` Ingo Molnar
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=20150128115800.000065fc@unknown \
--to=jesse.brandeburg@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--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 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.