From: Wolfram Sang <wsa@the-dreams.de>
To: "De Marchi, Lucas" <lucas.demarchi@intel.com>
Cc: "christian.ruppert@alitech.com" <christian.ruppert@alitech.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"mika.westerberg@linux.intel.com"
<mika.westerberg@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jarkko.nikula@linux.intel.com" <jarkko.nikula@linux.intel.com>
Subject: Re: [PATCH v3 0/3] i2c: designware: improve performance for transfers
Date: Tue, 16 Aug 2016 14:14:14 +0200 [thread overview]
Message-ID: <20160816121413.GB2846@tetsubishi> (raw)
In-Reply-To: <1471264451.2394.5.camel@intel.com>
[-- Attachment #1: Type: text/plain, Size: 240 bytes --]
> Looks like I forgot to CC Wolfram. CC'ing now on this cover letter, let
> me know if you also need the individual patches.
As long as the i2c-list is on cc, they will show up in patchwork and
then I'll have the patches. All fine here.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-08-16 12:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 22:03 [PATCH v3 0/3] i2c: designware: improve performance for transfers Lucas De Marchi
2016-07-28 22:03 ` [PATCH v3 1/3] i2c: designware: wait for disable/enable only if necessary Lucas De Marchi
2016-08-16 13:59 ` Jarkko Nikula
2016-07-28 22:03 ` [PATCH v3 2/3] i2c: designware: detect when dynamic tar update is possible Lucas De Marchi
2016-08-16 14:00 ` Jarkko Nikula
2016-08-16 14:07 ` De Marchi, Lucas
2016-08-17 8:05 ` Jarkko Nikula
2016-08-17 12:48 ` De Marchi, Lucas
2016-07-28 22:03 ` [PATCH v3 3/3] i2c: designware: do not disable adapter after transfer Lucas De Marchi
2016-08-16 14:00 ` Jarkko Nikula
2016-08-12 14:59 ` [PATCH v3 0/3] i2c: designware: improve performance for transfers Christian Ruppert
2016-08-15 12:34 ` De Marchi, Lucas
2016-08-16 12:14 ` 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=20160816121413.GB2846@tetsubishi \
--to=wsa@the-dreams.de \
--cc=christian.ruppert@alitech.com \
--cc=jarkko.nikula@linux.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