lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b5c00122-0fe0-4020-9036-e4cc37d1b51a@lunn.ch>
Date:   Tue, 25 Apr 2023 17:06:37 +0200
From:   Andrew Lunn <andrew@...n.ch>
To:     张网 <m202171703@...t.edu.cn>
Cc:     Peter Korsgaard <peter@...sgaard.com>,
        hust-os-kernel-patches@...glegroups.com, linux-i2c@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: Re: [PATCH v3] i2c: ocores: use devm_ managed clks

On Tue, Apr 25, 2023 at 10:47:29PM +0800, 张网 wrote:
> Hi Andrew,
> 
> I would like to express my sincere gratitude for taking the time and effort to review 
> my submitted patch. I understand that reviewing can be a time-consuming process 
> and I truly appreciate your dedication.
> 
> As we move forward, I would like to inquire about the first version[1] of the patch I submitted. 
> As clk_disable_unprepare() has checks for error pointer and NULL already, I think there is no 
> need to add the check. So both the first version of the patch and this one can work on this 
> branch.
> 
> If there are any further changes or revisions needed, please do not hesitate to let me know. 
> I am committed to learning and improving, and I welcome any feedback you may have. 
> Thank you again for your support and guidance throughout this process.
> 
> Best regards,
> Wang Zhang
> ---
> [1] http://patchwork.ozlabs.org/project/linux-i2c/patch/20230416071854.58335-1-silver_code@hust.edu.cn/

So this patch is about the IRQ being an error code, and doing the
correct cleanup.

With the change to devm_clk_get_ there is no need to disabled the
clock, it will be done automatically. This means there is no cleanup
the driver needs to do itself. So the patch is no longer needed.

    Andrew

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ