From: Tomoya MORINAGA <tomoya-linux@dsn.lapis-semi.com>
To: "Jeffrey (Sheng-Hui) Chu" <jeffchu@broadcom.com>
Cc: Jean Delvare <khali@linux-fr.org>,
Ben Dooks <ben-linux@fluff.org>,
Wolfram Sang <w.sang@pengutronix.de>, Qi Wang <qi.wang@intel.com>,
Linus Walleij <linus.walleij@stericsson.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"yong.y.wang@intel.com" <yong.y.wang@intel.com>,
"joel.clark@intel.com" <joel.clark@intel.com>,
"kok.howg.ewe@intel.com" <kok.howg.ewe@intel.com>
Subject: Re: [PATCH 2/7 v2] i2c-eg20t: delete 10bit access processing
Date: Thu, 06 Oct 2011 15:42:13 +0900 [thread overview]
Message-ID: <4E8D4DC5.3070701@dsn.lapis-semi.com> (raw)
In-Reply-To: <B6A520E9CD57404AAFC0831E4FB39541A9807DDCB7@IRVEXCHCCR02.corp.ad.broadcom.com>
(2011/10/06 2:29), Jeffrey (Sheng-Hui) Chu wrote:
> Is there any way I can help getting the code fixed instead of removed?
>
OK.
I will add a 10bit access code again.
I will post v3 patch series soon.
Please check the code.
--
tomoya
ROHM Co., Ltd.
next prev parent reply other threads:[~2011-10-06 6:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 4:17 [PATCH 1/7 v2] i2c-eg20t: Modify returned value s32 to long Tomoya MORINAGA
2011-10-05 4:17 ` [PATCH 2/7 v2] i2c-eg20t: delete 10bit access processing Tomoya MORINAGA
2011-10-05 17:29 ` Jeffrey (Sheng-Hui) Chu
2011-10-06 6:42 ` Tomoya MORINAGA [this message]
2011-10-05 4:17 ` [PATCH 3/7 v2] i2c-eg20t: Separate error processing Tomoya MORINAGA
2011-10-05 4:17 ` [PATCH 4/7 v2] i2c-eg20t: add stop sequence in case wait-event timeout occurs Tomoya MORINAGA
2011-10-05 4:17 ` [PATCH 5/7 v2] i2c-eg20t: Fix flag setting issue Tomoya MORINAGA
2011-10-05 4:17 ` [PATCH 6/7 v2] i2c-eg20t: Add initialize processing in case i2c-error occurs Tomoya MORINAGA
2011-10-05 4:17 ` [PATCH 7/7 v2] i2c-eg20t: Fix bus-idle waiting issue Tomoya MORINAGA
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=4E8D4DC5.3070701@dsn.lapis-semi.com \
--to=tomoya-linux@dsn.lapis-semi.com \
--cc=ben-linux@fluff.org \
--cc=jeffchu@broadcom.com \
--cc=joel.clark@intel.com \
--cc=khali@linux-fr.org \
--cc=kok.howg.ewe@intel.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qi.wang@intel.com \
--cc=w.sang@pengutronix.de \
--cc=yong.y.wang@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
all inboxes | Powered by JetHome®