From: alistair23@gmail.com (Alistair Francis)
To: linux-riscv@lists.infradead.org
Subject: [PATCH 4/4] irq-riscv-plic: Update function name
Date: Mon, 6 Aug 2018 16:30:43 -0700 [thread overview]
Message-ID: <CAKmqyKPApyiQ=okc69eD4dG5PZzyW84540cduCPpGzqvWZupzA@mail.gmail.com> (raw)
In-Reply-To: <20180806221009.12466-4-alistair.francis@wdc.com>
On Mon, Aug 6, 2018 at 3:10 PM, Alistair Francis
<alistair.francis@wdc.com> wrote:
> Update the function riscv_of_processor_hart() name to the new
> riscv_of_processor_hartid() name.
>
> Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
I am a little confused with how all these forks and branches work.
This series is meant for this branch:
https://github.com/riscv/riscv-linux/tree/riscv-all
I'll also submit a GitHub PR.
Alistair
> ---
> drivers/irqchip/irq-riscv-plic.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/irqchip/irq-riscv-plic.c b/drivers/irqchip/irq-riscv-plic.c
> index 99e79713abc6..9a94646fcd53 100644
> --- a/drivers/irqchip/irq-riscv-plic.c
> +++ b/drivers/irqchip/irq-riscv-plic.c
> @@ -343,7 +343,7 @@ static int plic_init(struct device_node *node, struct device_node *parent)
> /* skip any contexts that lead to inactive harts */
> if (of_device_is_compatible(parent.np, "riscv,cpu-intc") &&
> parent.np->parent &&
> - riscv_of_processor_hart(parent.np->parent) < 0)
> + riscv_of_processor_hartid(parent.np->parent) < 0)
> continue;
>
> parent_irq = irq_create_of_mapping(&parent);
> --
> 2.17.1
>
next prev parent reply other threads:[~2018-08-06 23:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 22:10 [PATCH 1/4] pcie-microsemi: Add support for the Vera-board root complex Alistair Francis
2018-08-06 22:10 ` [PATCH 2/4] riscv/smpboot: Fix mm_grab() typo Alistair Francis
2018-08-06 22:10 ` [PATCH 3/4] riscv/smpboot: Add missing include Alistair Francis
2018-08-06 22:10 ` [PATCH 4/4] irq-riscv-plic: Update function name Alistair Francis
2018-08-06 23:30 ` Alistair Francis [this message]
2018-08-20 21:16 ` Palmer Dabbelt
2018-08-06 23:13 ` [PATCH 1/4] pcie-microsemi: Add support for the Vera-board root complex Jonathan Neuschäfer
2018-08-06 23:34 ` Alistair Francis
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='CAKmqyKPApyiQ=okc69eD4dG5PZzyW84540cduCPpGzqvWZupzA@mail.gmail.com' \
--to=alistair23@gmail.com \
--cc=linux-riscv@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).