From: Christoph Hellwig <hch@infradead.org>
To: Anup Patel <anup@brainfault.org>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
Jason Cooper <jason@lakedaemon.net>,
Marc Zyngier <marc.zyngier@arm.com>,
Palmer Dabbelt <palmer@sifive.com>,
linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Atish Patra <atish.patra@wdc.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Thomas Gleixner <tglx@linutronix.de>,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v5 4/5] irqchip: sifive-plic: Differentiate between PLIC handler and context
Date: Mon, 11 Feb 2019 23:09:45 -0800 [thread overview]
Message-ID: <20190212070945.GF26747@infradead.org> (raw)
In-Reply-To: <20190119055625.100054-5-anup@brainfault.org>
Looks fine,
Reviewed-by: Christoph Hellwig <hch@lst.de>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-02-12 7:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 5:56 [PATCH v5 0/5] IRQ affinity support in PLIC driver Anup Patel
2019-01-19 5:56 ` [PATCH v5 1/5] irqchip: sifive-plic: Pre-compute context hart base and enable base Anup Patel
2019-02-12 7:11 ` Christoph Hellwig
2019-01-19 5:56 ` [PATCH v5 2/5] irqchip: sifive-plic: Don't inline plic_toggle() and plic_irq_toggle() Anup Patel
2019-02-12 7:09 ` Christoph Hellwig
2019-02-12 12:05 ` Anup Patel
2019-01-19 5:56 ` [PATCH v5 3/5] irqchip: sifive-plic: Add warning in plic_init() if handler already present Anup Patel
2019-01-19 5:56 ` [PATCH v5 4/5] irqchip: sifive-plic: Differentiate between PLIC handler and context Anup Patel
2019-02-12 7:09 ` Christoph Hellwig [this message]
2019-01-19 5:56 ` [PATCH v5 5/5] irqchip: sifive-plic: Implement irq_set_affinity() for SMP host Anup Patel
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=20190212070945.GF26747@infradead.org \
--to=hch@infradead.org \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@wdc.com \
--cc=daniel.lezcano@linaro.org \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=palmer@sifive.com \
--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).