From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Petr Cvek <petr.cvek-qphu/3gb4gc@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org
Subject: Re: [PATCH v3] i2c-pxa: add support for SCCB devices
Date: Tue, 25 Nov 2014 15:26:33 +0100 [thread overview]
Message-ID: <20141125142633.GE1843@katana> (raw)
In-Reply-To: <54740E1D.9060508-qphu/3gb4gc@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 447 bytes --]
On Tue, Nov 25, 2014 at 06:05:33AM +0100, Petr Cvek wrote:
> Fixed missing functionality flag I2C_FUNC_NOSTART.
>
> Added support for SCCB by implementing I2C_M_IGNORE_NAK and I2C_M_STOP flag and belonging functionality flag I2C_FUNC_PROTOCOL_MANGLING.
>
> Signed-off-by: Petr Cvek <petr.cvek-qphu/3gb4gc@public.gmane.org>
Applied to for-next, thanks!
Please send new patches as seperate threads, not as a reply to the old
patch.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-11-25 14:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-22 22:52 [PATCH] Add support for SCCB devices into PXA27x I2C controller Petr Cvek
[not found] ` <54711397.9060601-qphu/3gb4gc@public.gmane.org>
2014-11-23 8:31 ` Wolfram Sang
2014-11-23 22:21 ` [PATCH v2] " Petr Cvek
[not found] ` <54725DE2.9090800-qphu/3gb4gc@public.gmane.org>
2014-11-24 17:27 ` Wolfram Sang
2014-11-25 5:05 ` [PATCH v3] i2c-pxa: add support for SCCB devices Petr Cvek
[not found] ` <54740E1D.9060508-qphu/3gb4gc@public.gmane.org>
2014-11-25 14:26 ` Wolfram Sang [this message]
2014-11-23 16:23 ` [PATCH] Add support for SCCB devices into PXA27x I2C controller Sergei Shtylyov
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=20141125142633.GE1843@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=petr.cvek-qphu/3gb4gc@public.gmane.org \
--cc=sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org \
/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).