From: Christoph Hellwig <hch@lst.de>
To: "Guilherme G. Piccoli" <gpiccoli@linux.vnet.ibm.com>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
gabriel@krisman.be, hch@lst.de, linuxppc-dev@lists.ozlabs.org,
linux-pci@vger.kernel.org, stable@vger.kernel.org.#.v4.9+
Subject: Re: [PATCH] genirq/affinity: fix node generation from cpumask
Date: Thu, 15 Dec 2016 09:54:56 +0100 [thread overview]
Message-ID: <20161215085456.GA2864@lst.de> (raw)
In-Reply-To: <1481738472-2671-1-git-send-email-gpiccoli@linux.vnet.ibm.com>
Looks fine:
Reviewed-by: Christoph Hellwig <hch@lst.de>
(but I agree with the bracing nitpick from Gavin)
next prev parent reply other threads:[~2016-12-15 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 18:01 [PATCH] genirq/affinity: fix node generation from cpumask Guilherme G. Piccoli
2016-12-14 23:24 ` Gavin Shan
2016-12-15 9:36 ` Thomas Gleixner
2016-12-15 12:38 ` Guilherme G. Piccoli
2016-12-15 1:05 ` Gabriel Krisman Bertazi
2016-12-15 8:54 ` Christoph Hellwig [this message]
2016-12-15 12:34 ` Balbir Singh
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=20161215085456.GA2864@lst.de \
--to=hch@lst.de \
--cc=gabriel@krisman.be \
--cc=gpiccoli@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=stable@vger.kernel.org.#.v4.9+ \
--cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).