From: Octavian Purdila <octavian.purdila-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
Cc: wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org,
julia.lawall-L2FTfq7BK8M@public.gmane.org,
dan.carpenter-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org,
johan-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Octavian Purdila
<octavian.purdila-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: [PATCH v2 0/4] dln2 fixes for ib-mfd-gpio-i2c-3.19
Date: Tue, 18 Nov 2014 14:57:56 +0200 [thread overview]
Message-ID: <1416315480-2053-1-git-send-email-octavian.purdila@intel.com> (raw)
Hi Lee,
Here are a few fixes for the DLN2 drivers for the ib-mfd-gpio-i2c-3.19 branch.
Thanks,
Tavi
Changes since v1:
* fix coding style (add braces) and remove redundant ret = 0 statement
* add two more fixes for issues reported by Dan Carpenter
Dan Carpenter (1):
mfd: dln2: a couple endian fixes
Octavian Purdila (3):
mfd: dln2: fix _dln2_transfer return code
i2c: dln2: simplify return flow for dln2_i2c_enable
mfd: dln2: add a limit check for invalid echo
drivers/i2c/busses/i2c-dln2.c | 7 +------
drivers/mfd/dln2.c | 18 ++++++++++++------
2 files changed, 13 insertions(+), 12 deletions(-)
--
1.9.1
next reply other threads:[~2014-11-18 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 12:57 Octavian Purdila [this message]
2014-11-18 12:57 ` [PATCH v2 1/4] mfd: dln2: fix _dln2_transfer return code Octavian Purdila
2014-11-18 12:57 ` [PATCH v2 2/4] i2c: dln2: simplify return flow for dln2_i2c_enable Octavian Purdila
2014-11-18 12:57 ` [PATCH v2 3/4] mfd: dln2: add a limit check for invalid echo Octavian Purdila
2014-11-18 12:58 ` [PATCH v2 4/4] mfd: dln2: a couple endian fixes Octavian Purdila
[not found] ` <1416315480-2053-1-git-send-email-octavian.purdila-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-11-19 17:34 ` [GIT PULL] Immutable branch between MFD, GPIO and I2C (Second batch) Lee Jones
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=1416315480-2053-1-git-send-email-octavian.purdila@intel.com \
--to=octavian.purdila-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=dan.carpenter-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=johan-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=julia.lawall-L2FTfq7BK8M@public.gmane.org \
--cc=lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@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).