From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Liu Peibao <loven.liu@jaguarmicro.com>,
Andi Shyti <andi.shyti@kernel.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Jan Dabros <jsd@semihalf.com>,
"xiaowu . ding" <xiaowu.ding@jaguarmicro.com>,
Angus Chen <angus.chen@jaguarmicro.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND TO CC MAILLIST] i2c: designware: fix master holding SCL low when I2C_DYNAMIC_TAR_UPDATE not set
Date: Wed, 6 Nov 2024 13:53:17 +0200 [thread overview]
Message-ID: <bac8d1ea-ed0f-42db-a0f8-c36d7c571534@linux.intel.com> (raw)
In-Reply-To: <bfc14b55-35e1-479c-bd9b-d40d1ea88377@jaguarmicro.com>
On 11/6/24 12:09 PM, Liu Peibao wrote:
> On 2024/11/6 17:46, Andi Shyti wrote:
>>> Fixes: 2409205acd3c ("i2c: designware: fix __i2c_dw_disable() in case master is holding SCL low")
>>> Co-developed-by: xiaowu.ding <xiaowu.ding@jaguarmicro.com>
>>> Signed-off-by: xiaowu.ding <xiaowu.ding@jaguarmicro.com>
>>> Co-developed-by: Angus Chen <angus.chen@jaguarmicro.com>
>>> Signed-off-by: Angus Chen <angus.chen@jaguarmicro.com>
>>> Signed-off-by: Liu Peibao <loven.liu@jaguarmicro.com>
>>
>> Thanks, this make much more sense now.
>>
>> Just one question, do we want to keep xiaowu.ding or Xiaowu Ding?
>> Can I change it to the second way? It looks better and that's how
>> it's normally signed.
>>
>
> I have confirmed with Xiaowu, and that is surely okay.
>
Acked-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
next prev parent reply other threads:[~2024-11-06 11:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 8:12 [PATCH RESEND TO CC MAILLIST] i2c: designware: fix master holding SCL low when I2C_DYNAMIC_TAR_UPDATE not set Liu Peibao
2024-11-01 8:44 ` Andy Shevchenko
2024-11-01 10:18 ` Liu Peibao
2024-11-05 20:30 ` Andi Shyti
2024-11-06 7:27 ` Liu Peibao
2024-11-06 9:46 ` Andi Shyti
2024-11-06 10:09 ` Liu Peibao
2024-11-06 11:53 ` Jarkko Nikula [this message]
2024-11-06 23:07 ` 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=bac8d1ea-ed0f-42db-a0f8-c36d7c571534@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=andi.shyti@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=angus.chen@jaguarmicro.com \
--cc=jsd@semihalf.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loven.liu@jaguarmicro.com \
--cc=mika.westerberg@linux.intel.com \
--cc=xiaowu.ding@jaguarmicro.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