From: Wei Ni <wni@nvidia.com>
To: "khali@linux-fr.org" <khali@linux-fr.org>,
"ben-linux@fluff.org" <ben-linux@fluff.org>,
"lucas.demarchi@profusion.mobi" <lucas.demarchi@profusion.mobi>,
"ccross@android.com" <ccross@android.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 0/2] i2c: tegra: add some new features for tegra i2c
Date: Wed, 27 Apr 2011 18:25:51 +0800 [thread overview]
Message-ID: <6B4D417B830BC44B8026029FD256F7F1C2CB3DD4DB@HKMAIL01.nvidia.com> (raw)
In-Reply-To: <1303301312-15302-1-git-send-email-wni@nvidia.com>
Hi, all
Could anyone review these changes?
Thanks
Wei.
-----Original Message-----
From: Wei Ni
Sent: Wednesday, April 20, 2011 8:09 PM
To: khali@linux-fr.org; ben-linux@fluff.org; lucas.demarchi@profusion.mobi; ccross@android.com; linux-i2c@vger.kernel.org; linux-kernel@vger.kernel.org
Cc: Wei Ni
Subject: [PATCH 0/2] i2c: tegra: add some new features for tegra i2c
From: Wei Ni <wni@nvidia.com>
*** BLURB HERE ***
Wei Ni (2):
i2c: tegra: Retry transfer when unexpected/no_ack status is detected
i2c: tegra: use new i2c slave controller
drivers/i2c/busses/i2c-tegra.c | 57 +++++++++++++++++++++++++++++++++++++--
include/linux/i2c-tegra.h | 3 ++
2 files changed, 57 insertions(+), 3 deletions(-)
next prev parent reply other threads:[~2011-04-27 10:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 12:08 wni
2011-04-20 12:08 ` [PATCH 1/2] i2c: tegra: Retry transfer when unexpected/no_ack status is detected wni
2011-04-20 12:08 ` [PATCH 2/2] i2c: tegra: use new i2c slave controller wni
2011-04-27 10:25 ` Wei Ni [this message]
2011-04-27 16:29 ` [PATCH 0/2] i2c: tegra: add some new features for tegra i2c Stephen Warren
2011-04-29 6:08 ` Wei Ni
2011-04-29 15:20 ` Stephen Warren
2011-05-04 3:03 ` Wei Ni
2011-05-04 8:28 ` Marc Dietrich
2011-05-04 9:19 ` Wei Ni
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=6B4D417B830BC44B8026029FD256F7F1C2CB3DD4DB@HKMAIL01.nvidia.com \
--to=wni@nvidia.com \
--cc=ben-linux@fluff.org \
--cc=ccross@android.com \
--cc=khali@linux-fr.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@profusion.mobi \
/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
all inboxes | Powered by JetHome®