From: Andrew Lunn <andrew@lunn.ch>
To: 张网 <m202171703@hust.edu.cn>
Cc: Peter Korsgaard <peter@korsgaard.com>,
hust-os-kernel-patches@googlegroups.com,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH v3] i2c: ocores: use devm_ managed clks
Date: Tue, 25 Apr 2023 17:06:37 +0200 [thread overview]
Message-ID: <b5c00122-0fe0-4020-9036-e4cc37d1b51a@lunn.ch> (raw)
In-Reply-To: <85952de.43bfe.187b8e24612.Coremail.m202171703@hust.edu.cn>
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
next prev parent reply other threads:[~2023-04-25 15:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 7:20 [PATCH] i2c: ocores: add missing unwind goto in `ocores_i2c_probe` Wang Zhang
2023-04-16 15:33 ` Andrew Lunn
2023-04-17 13:27 ` [PATCH v2] i2c: ocores: use devm_ managed clks Wang Zhang
2023-04-17 14:05 ` Wang Zhang
2023-04-17 14:29 ` Peter Rosin
2023-04-17 15:50 ` Andrew Lunn
2023-04-22 12:32 ` [PATCH v3] " Wang Zhang
2023-04-25 9:58 ` 张网
2023-04-25 11:57 ` Andrew Lunn
2023-04-25 14:47 ` 张网
2023-04-25 15:06 ` Andrew Lunn [this message]
2023-05-26 7:05 ` [PATCH v4] " Wang Zhang
2023-06-13 23:54 ` Andi Shyti
2023-06-23 8:22 ` Wolfram Sang
2023-06-23 8:26 ` Wolfram Sang
2023-05-23 4:49 ` Re: [PATCH v3] " 张网
2023-05-23 12:10 ` Andrew Lunn
2023-05-23 14:33 ` Wang Zhang
2023-05-24 15:35 ` Wang Zhang
2023-05-24 15:43 ` Wang Zhang
2023-05-24 18:45 ` Dan Carpenter
2023-05-24 19:21 ` Christophe JAILLET
2023-05-25 3:33 ` 张网
2023-05-25 19:16 ` Christophe JAILLET
2023-05-25 5:05 ` Dan Carpenter
2023-05-25 5:02 ` Dan Carpenter
2023-05-25 9:28 ` Dan Carpenter
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=b5c00122-0fe0-4020-9036-e4cc37d1b51a@lunn.ch \
--to=andrew@lunn.ch \
--cc=hust-os-kernel-patches@googlegroups.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m202171703@hust.edu.cn \
--cc=peter@korsgaard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®