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:   Mon, 28 Nov 2022 10:30:05 +0000
From:   "Russell King (Oracle)" <linux@armlinux.org.uk>
To:     Zhen Lei <thunder.leizhen@huawei.com>
Cc:     Ard Biesheuvel <ardb@kernel.org>,
        linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] ARM: Make the dumped instructions are consistent
 with the disassembled ones
Message-ID: <Y4SNrQgON1qY9vzE@shell.armlinux.org.uk>
References: <20221126122137.2025-1-thunder.leizhen@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20221126122137.2025-1-thunder.leizhen@huawei.com>
Sender: Russell King (Oracle) <linux@armlinux.org.uk>
Precedence: bulk

On Sat, Nov 26, 2022 at 08:21:35PM +0800, Zhen Lei wrote:
> v3 --> v4:
> 1. The sparse warnings that are not involved in the modification are
>    not eliminated.
> 2. Eliminate the sparse warnings involved in the modification when
>    refactor dump_instr(), no longer use a separate patch.
> 
> v2 --> v3:
> 1. Don't use '__force to' cleanup the sparse warnings
> 2. Refactor dump_instr()
> 3. Relace cpu_to_le{32|16}() with __mem_to_opcode_{arm|thumb16}()
> 
> 
> v1 --> v2:
> 1. Cleanup sparse warnings.
> 
> Zhen Lei (2):
>   ARM: Refactor dump_instr()
>   ARM: Make the dumped instructions are consistent with the disassembled
>     ones

Looks good now, thanks.

Please put it in my patch system, details in my signature. Thanks.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!