From: Conor Dooley <conor.dooley@microchip.com>
To: Evgenii Shatokhin <e.shatokhin@yadro.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Daire McNamara <daire.mcnamara@microchip.com>,
Anup Patel <anup@brainfault.org>,
Atish Patra <atishp@rivosinc.com>,
Nick Kossifidis <mick@ics.forth.gr>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
"Valentina Fernandez" <valentina.fernandezalanis@microchip.com>
Subject: Re: [PATCH v1] riscv: fix reserved memory setup
Date: Tue, 8 Nov 2022 07:27:01 +0000 [thread overview]
Message-ID: <Y2oExSUbPoziPyjt@wendy> (raw)
In-Reply-To: <497c057d-4e7d-0dcb-fd4c-2c7ef6efb573@yadro.com>
On Tue, Nov 08, 2022 at 12:40:19AM +0300, Evgenii Shatokhin wrote:
> Hi,
> Thank you for looking into this!
>
> As I wrote earlier, I ran into this issue too, while working on a remoteproc
> driver for our RISC-V-based SoC.
>
> The proposed patch fixes the bug for me and seems to have no problematic
> side-effects. So:
>
> Tested-by: Evgenii Shatokhin <e.shatokhin@yadro.com>
Apologies for forgetting to add the T-b tag & thanks for re-sending it.
Conor.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor.dooley@microchip.com>
To: Evgenii Shatokhin <e.shatokhin@yadro.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Daire McNamara <daire.mcnamara@microchip.com>,
Anup Patel <anup@brainfault.org>,
Atish Patra <atishp@rivosinc.com>,
Nick Kossifidis <mick@ics.forth.gr>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
"Valentina Fernandez" <valentina.fernandezalanis@microchip.com>
Subject: Re: [PATCH v1] riscv: fix reserved memory setup
Date: Tue, 8 Nov 2022 07:27:01 +0000 [thread overview]
Message-ID: <Y2oExSUbPoziPyjt@wendy> (raw)
In-Reply-To: <497c057d-4e7d-0dcb-fd4c-2c7ef6efb573@yadro.com>
On Tue, Nov 08, 2022 at 12:40:19AM +0300, Evgenii Shatokhin wrote:
> Hi,
> Thank you for looking into this!
>
> As I wrote earlier, I ran into this issue too, while working on a remoteproc
> driver for our RISC-V-based SoC.
>
> The proposed patch fixes the bug for me and seems to have no problematic
> side-effects. So:
>
> Tested-by: Evgenii Shatokhin <e.shatokhin@yadro.com>
Apologies for forgetting to add the T-b tag & thanks for re-sending it.
Conor.
next prev parent reply other threads:[~2022-11-08 7:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 15:15 [PATCH v1] riscv: fix reserved memory setup Conor Dooley
2022-11-07 15:15 ` Conor Dooley
2022-11-07 21:40 ` Evgenii Shatokhin
2022-11-07 21:40 ` Evgenii Shatokhin
2022-11-08 7:27 ` Conor Dooley [this message]
2022-11-08 7:27 ` Conor Dooley
2022-11-10 22:54 ` Palmer Dabbelt
2022-11-10 22:54 ` Palmer Dabbelt
2022-11-10 23:10 ` patchwork-bot+linux-riscv
2022-11-10 23:10 ` patchwork-bot+linux-riscv
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=Y2oExSUbPoziPyjt@wendy \
--to=conor.dooley@microchip.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@rivosinc.com \
--cc=daire.mcnamara@microchip.com \
--cc=e.shatokhin@yadro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mick@ics.forth.gr \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=valentina.fernandezalanis@microchip.com \
/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.