From: liudingyuan <liudingyuan@huawei.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: yangyicong <yangyicong@huawei.com>,
"Fangjian (Jay)" <f.fangjian@huawei.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: 答复: [PATCH v2 0/2] i2c: hisi: Clear the interrupt status and optimize writing limitation
Date: Thu, 1 Feb 2024 07:48:24 +0000 [thread overview]
Message-ID: <40cce35e91044e5889ee140deef8daff@huawei.com> (raw)
In-Reply-To: <mjkxuorj3ldxa2yi3axeuy375cida3n4lubfjudw5jcbjfi3x4@htnwzbjw2tl3>
Hi Andi
Thanks for replying. I will remember to refer to the patches submitted by others to write the modifications in different versions of patches. Also will add review-by info.
Thanks,
Devyn
-----邮件原件-----
发件人: Andi Shyti <andi.shyti@kernel.org>
发送时间: 2024年2月1日 14:50
收件人: liudingyuan <liudingyuan@huawei.com>
抄送: yangyicong <yangyicong@huawei.com>; Fangjian (Jay) <f.fangjian@huawei.com>; Jonathan Cameron <jonathan.cameron@huawei.com>; linux-i2c@vger.kernel.org
主题: Re: [PATCH v2 0/2] i2c: hisi: Clear the interrupt status and optimize writing limitation
Hi Devyn,
On Thu, Feb 01, 2024 at 02:13:43PM +0800, Devyn Liu wrote:
> Devyn Liu (2):
> i2c: hisi: Optimized the value setting of maxwrite limit to fifo depth
> - 1
> i2c: hisi: Add clearing tx aempty interrupt operation
please, next time add the changelog. What is the difference between v1 and v2?
Besides that, you forgot to add Yicong's r-b.
Don't need to resend, will take care of it.
Andi
next prev parent reply other threads:[~2024-02-01 7:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 6:13 [PATCH v2 0/2] i2c: hisi: Clear the interrupt status and optimize writing limitation Devyn Liu
2024-02-01 6:13 ` [PATCH v2 1/2] i2c: hisi: Optimized the value setting of maxwrite limit to fifo depth - 1 Devyn Liu
2024-02-01 6:51 ` Andi Shyti
2024-02-01 7:47 ` 答复: " liudingyuan
2024-02-01 6:13 ` [PATCH v2 2/2] i2c: hisi: Add clearing tx aempty interrupt operation Devyn Liu
2024-02-01 6:52 ` Andi Shyti
2024-02-01 6:49 ` [PATCH v2 0/2] i2c: hisi: Clear the interrupt status and optimize writing limitation Andi Shyti
2024-02-01 7:48 ` liudingyuan [this message]
2024-02-01 23:33 ` Andi Shyti
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=40cce35e91044e5889ee140deef8daff@huawei.com \
--to=liudingyuan@huawei.com \
--cc=andi.shyti@kernel.org \
--cc=f.fangjian@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-i2c@vger.kernel.org \
--cc=yangyicong@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.