public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Yicong Yang <yangyicong@huawei.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Devyn Liu <liudingyuan@huawei.com>, <yangyicong@hisilicon.com>,
	<f.fangjian@huawei.com>, <jonathan.cameron@huawei.com>,
	<linux-i2c@vger.kernel.org>
Subject: Re: [PATCH]i2c: hisi: Clear the interrupt status and optimize writing limitation
Date: Thu, 1 Feb 2024 10:12:09 +0800	[thread overview]
Message-ID: <2e0660cf-e4c7-d905-d5d6-edf0a0079d7a@huawei.com> (raw)
In-Reply-To: <bcprziyqs7cze34j52z4uplxjdqtlvdgat32us347wgb4hv4gm@rtmqlz4c6ie2>

On 2024/2/1 6:47, Andi Shyti wrote:
> On Tue, Jan 23, 2024 at 04:02:20PM +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
> 
> The series looks good to me.
> 
> Yicong, any thought?
> 

Sorry for finding this late. Generally looks good to me as well and just replied.

> Thanks,
> Andi
> 
>>
>>  drivers/i2c/busses/i2c-hisi.c | 13 ++++++++++++-
>>  1 file changed, 12 insertions(+), 1 deletion(-)
>>
>> -- 
>> 2.30.0
>>
> .
> 

  reply	other threads:[~2024-02-01  2:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23  8:02 [PATCH]i2c: hisi: Clear the interrupt status and optimize writing limitation Devyn Liu
2024-01-23  8:02 ` [PATCH 1/2] i2c: hisi: Optimized the value setting of maxwrite limit to fifo depth - 1 Devyn Liu
2024-02-01  2:06   ` Yicong Yang
2024-01-23  8:02 ` [PATCH 2/2] i2c: hisi: Add clearing tx aempty interrupt operation Devyn Liu
2024-02-01  2:06   ` Yicong Yang
2024-01-31 22:47 ` [PATCH]i2c: hisi: Clear the interrupt status and optimize writing limitation Andi Shyti
2024-02-01  2:12   ` Yicong Yang [this message]
2024-02-01  6:47     ` 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=2e0660cf-e4c7-d905-d5d6-edf0a0079d7a@huawei.com \
    --to=yangyicong@huawei.com \
    --cc=andi.shyti@kernel.org \
    --cc=f.fangjian@huawei.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=liudingyuan@huawei.com \
    --cc=yangyicong@hisilicon.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