From: shubhrajyoti@ti.com (Shubhrajyoti)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 3/7] i2c: omap: remove the dtrev
Date: Mon, 5 Nov 2012 14:56:23 +0530 [thread overview]
Message-ID: <5097863F.7030105@ti.com> (raw)
In-Reply-To: <20121105090517.GB2913@arwen.pp.htv.fi>
On Monday 05 November 2012 02:35 PM, Felipe Balbi wrote:
>> egister map is different.
>> >
>> > So the scheme may still be required.
> fair enough, but drop it from debugging messages.
OK thanks.
next prev parent reply other threads:[~2012-11-05 9:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-04 10:44 [PATCHv2 0/7] i2c: omap: updates Shubhrajyoti D
2012-11-04 10:44 ` [PATCHv2 1/7] i2c: omap: Fix the revision register read Shubhrajyoti D
2012-11-05 7:50 ` Felipe Balbi
2012-11-05 8:34 ` Shubhrajyoti
2012-11-05 9:04 ` Felipe Balbi
2012-11-05 9:24 ` Shubhrajyoti Datta
2012-11-05 10:01 ` Felipe Balbi
2012-11-05 10:45 ` Felipe Balbi
2012-11-05 9:40 ` Shubhrajyoti Datta
2012-11-04 10:44 ` [PATCHv2 2/7] i2c: omap: use revision check for OMAP_I2C_FLAG_APPLY_ERRATA_I207 Shubhrajyoti D
2012-11-05 7:51 ` Felipe Balbi
2012-11-04 10:44 ` [PATCHv2 3/7] i2c: omap: remove the dtrev Shubhrajyoti D
2012-11-05 7:53 ` Felipe Balbi
2012-11-05 8:44 ` Shubhrajyoti
2012-11-05 9:05 ` Felipe Balbi
2012-11-05 9:26 ` Shubhrajyoti [this message]
2012-11-04 10:44 ` [PATCHv2 4/7] ARM: i2c: omap: Remove the i207 errata flag Shubhrajyoti D
2012-11-05 7:53 ` Felipe Balbi
2012-11-04 10:44 ` [PATCHv2 5/7] i2c: omap: re-factor omap_i2c_init function Shubhrajyoti D
2012-11-05 7:54 ` Felipe Balbi
2012-11-04 10:44 ` [PATCHv2 6/7] i2c: omap: make reset a seperate function Shubhrajyoti D
2012-11-05 7:55 ` Felipe Balbi
2012-11-04 10:44 ` [PATCHv2 7/7] i2c: omap: Restore i2c context always Shubhrajyoti D
2012-11-05 7:56 ` Felipe Balbi
2012-11-05 7:46 ` [PATCHv2 0/7] i2c: omap: updates Felipe Balbi
2012-11-05 8:34 ` Shubhrajyoti
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=5097863F.7030105@ti.com \
--to=shubhrajyoti@ti.com \
--cc=linux-arm-kernel@lists.infradead.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).