From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Andrey Utkin <andrey_utkin@fastmail.com>,
Lucas De Marchi <lucas.demarchi@intel.com>
Cc: linux-i2c@vger.kernel.org,
"Christian Ruppert" <christian.ruppert@alitech.com>,
mika.westerberg@linux.intel.com, linux-kernel@vger.kernel.org,
"Wolfram Sang" <wsa@the-dreams.de>,
"José Roberto de Souza" <jose.souza@intel.com>
Subject: Re: [PATCH v4 1/4] i2c: designware: wait for disable/enable only if necessary
Date: Mon, 27 Mar 2017 11:29:25 +0300 [thread overview]
Message-ID: <177eece4-0b16-b4b8-5280-a4981a01865a@linux.intel.com> (raw)
In-Reply-To: <20170326194459.GB4209@dell-m4800.Home>
On 03/26/2017 10:44 PM, Andrey Utkin wrote:
> Regression reported: https://bugzilla.kernel.org/show_bug.cgi?id=194969
>
Thanks, I commented the bug.
--
Jarkko
next prev parent reply other threads:[~2017-03-27 8:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 22:18 [PATCH v4 0/4] i2c: designware: improve performance for transfers Lucas De Marchi
2016-08-23 22:18 ` [PATCH v4 1/4] i2c: designware: wait for disable/enable only if necessary Lucas De Marchi
2017-03-26 19:44 ` Andrey Utkin
2017-03-27 8:29 ` Jarkko Nikula [this message]
2016-08-23 22:18 ` [PATCH v4 2/4] i2c: designware: add common functions for locking Lucas De Marchi
2016-08-23 22:18 ` [PATCH v4 3/4] i2c: designware: detect when dynamic tar update is possible Lucas De Marchi
2016-08-25 20:03 ` Wolfram Sang
2016-08-23 22:18 ` [PATCH v4 4/4] i2c: designware: do not disable adapter after transfer Lucas De Marchi
2016-08-24 10:31 ` [PATCH v4 0/4] i2c: designware: improve performance for transfers Jarkko Nikula
2016-08-25 16:23 ` Christian Ruppert
2016-08-25 20:07 ` Wolfram Sang
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=177eece4-0b16-b4b8-5280-a4981a01865a@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=andrey_utkin@fastmail.com \
--cc=christian.ruppert@alitech.com \
--cc=jose.souza@intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=wsa@the-dreams.de \
/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).