From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] irq/affinity: Assign all CPUs a vector
Date: Thu, 30 Mar 2017 10:21:06 +0200 [thread overview]
Message-ID: <20170330082106.GC11344@lst.de> (raw)
In-Reply-To: <1490743277-14139-1-git-send-email-keith.busch@intel.com>
Looks fine,
Reviewed-by: Christoph Hellwig <hch at lst.de>
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <keith.busch@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
Thomas Gleixner <tglx@linutronix.de>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] irq/affinity: Assign all CPUs a vector
Date: Thu, 30 Mar 2017 10:21:06 +0200 [thread overview]
Message-ID: <20170330082106.GC11344@lst.de> (raw)
In-Reply-To: <1490743277-14139-1-git-send-email-keith.busch@intel.com>
Looks fine,
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2017-03-30 8:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 23:21 [PATCH] irq/affinity: Assign all CPUs a vector Keith Busch
2017-03-28 23:21 ` Keith Busch
2017-03-29 17:15 ` Sagi Grimberg
2017-03-29 17:15 ` Sagi Grimberg
2017-03-29 17:54 ` Keith Busch
2017-03-29 17:54 ` Keith Busch
2017-03-29 17:50 ` Sagi Grimberg
2017-03-29 17:50 ` Sagi Grimberg
2017-03-30 8:21 ` Christoph Hellwig [this message]
2017-03-30 8:21 ` Christoph Hellwig
2017-03-30 17:12 ` Keith Busch
2017-03-30 17:12 ` Keith Busch
2017-04-12 1:33 ` [lkp-robot] [irq/affinity] 13c024422c: fsmark.files_per_sec -4.3% regression kernel test robot
2017-04-12 1:33 ` kernel test robot
2017-04-12 1:33 ` kernel test robot
2017-04-12 13:52 ` Busch, Keith
2017-04-13 1:06 ` Ye Xiaolong
2017-04-13 14:24 ` Keith Busch
2017-04-13 17:14 ` Busch, Keith
2017-04-14 0:49 ` Ye Xiaolong
2017-04-12 15:02 ` Keith Busch
2017-04-12 15:02 ` Keith Busch
2017-04-12 15:02 ` Keith Busch
2017-03-31 10:59 ` [PATCH] irq/affinity: Assign all CPUs a vector Thomas Gleixner
2017-03-31 10:59 ` Thomas Gleixner
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=20170330082106.GC11344@lst.de \
--to=hch@lst.de \
/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.