Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 8 Nov 2022 07:27:01 +0000
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
Message-ID: <Y2oExSUbPoziPyjt@wendy>
References: <20221107151524.3941467-1-conor.dooley@microchip.com>
 <497c057d-4e7d-0dcb-fd4c-2c7ef6efb573@yadro.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <497c057d-4e7d-0dcb-fd4c-2c7ef6efb573@yadro.com>
Precedence: bulk

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.