From: Wolfram Sang <wsa@kernel.org>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: David Zheng <david.zheng@intel.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
andriy.shevchenko@linux.intel.com,
mika.westerberg@linux.intel.com, jsd@semihalf.com
Subject: Re: [PATCH v3] i2c: designware: fix idx_write_cnt in read loop
Date: Mon, 5 Jun 2023 14:36:44 +0200 [thread overview]
Message-ID: <ZH3W3M4gJn98gePX@shikoro> (raw)
In-Reply-To: <ed2cbf76-1868-9153-81c7-cc17b807421e@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 100 bytes --]
> In my opinion this patch is more improvement rather than a regression fix.
Okay, then, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-06-05 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 18:14 [PATCH v3] i2c: designware: fix idx_write_cnt in read loop David Zheng
2023-05-26 13:58 ` Jarkko Nikula
2023-06-05 10:02 ` Wolfram Sang
2023-06-05 10:48 ` Jarkko Nikula
2023-06-05 12:36 ` Wolfram Sang [this message]
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=ZH3W3M4gJn98gePX@shikoro \
--to=wsa@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=david.zheng@intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jsd@semihalf.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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;
as well as URLs for NNTP newsgroup(s).