From: Wolfram Sang <wsa@the-dreams.de>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: linux-i2c@vger.kernel.org,
"Christian Ruppert" <christian.ruppert@alitech.com>,
mika.westerberg@linux.intel.com, jarkko.nikula@linux.intel.com,
linux-kernel@vger.kernel.org,
"José Roberto de Souza" <jose.souza@intel.com>
Subject: Re: [PATCH v4 3/4] i2c: designware: detect when dynamic tar update is possible
Date: Thu, 25 Aug 2016 22:03:24 +0200 [thread overview]
Message-ID: <20160825200324.GE1614@katana> (raw)
In-Reply-To: <1471990736-30190-4-git-send-email-lucas.demarchi@intel.com>
[-- Attachment #1: Type: text/plain, Size: 256 bytes --]
> + u32 ic_con = dw_readl(dev, DW_IC_CON);
> + if (msgs[dev->msg_write_idx].flags & I2C_M_TEN)
Checkpatch warned:
WARNING: Missing a blank line after declarations
#49: FILE: drivers/i2c/busses/i2c-designware-core.c:452:
I fixed it for you this time.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-25 20:04 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
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 [this message]
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=20160825200324.GE1614@katana \
--to=wsa@the-dreams.de \
--cc=christian.ruppert@alitech.com \
--cc=jarkko.nikula@linux.intel.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 \
/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).