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;
Subject: Re: [PATCH] clk: microchip: check for null return of devm_kzalloc()
To:     Conor Dooley <conor@kernel.org>
References: <20221119054858.178629-1-tanghui20@huawei.com>
 <Y3izOuF56/NywpOR@spud>
CC:     <mturquette@baylibre.com>, <sboyd@kernel.org>,
        <linux-clk@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
        <yusongping@huawei.com>, <claudiu.beznea@microchip.com>,
        <conor.dooley@microchip.com>
From:   Hui Tang <tanghui20@huawei.com>
Message-ID: <39867664-1c14-9628-a82f-a9682a22c5f8@huawei.com>
Date:   Mon, 21 Nov 2022 15:26:44 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <Y3izOuF56/NywpOR@spud>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk


On 2022/11/19 18:43, Conor Dooley wrote:
> On Sat, Nov 19, 2022 at 01:48:58PM +0800, Hui Tang wrote:
>> Because of the possilble failure of devm_kzalloc(), name might be NULL and
>> will cause null pointer derefrence later.
>
> In theory, yeah?
>
> (note to self, s/refrence/reference/, s/possilble/possible)

Sorry, I make spelling mistakes.

Thanks.