linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Nikula <jhnikula@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
	Ben Dooks <ben-linux@fluff.org>,
	Cory Maccarrone <darkstar6262@gmail.com>,
	linux-omap@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH v2] [I2C-OMAP] Add support for 16-bit registers
Date: Fri, 19 Mar 2010 11:05:09 +0200	[thread overview]
Message-ID: <20100319110509.76784df2.jhnikula@gmail.com> (raw)
In-Reply-To: <20100310223000.GT2900@atomide.com>

On Wed, 10 Mar 2010 14:30:00 -0800
Tony Lindgren <tony@atomide.com> wrote:

> * Kevin Hilman <khilman@deeprootsystems.com> [100310 10:01]:
> > Tony Lindgren <tony@atomide.com> writes:
> > 
...
> > Unfortunately, Tony's additional fix did not make it into the version
> > that was merged to mainline, which results in a crash during
> > probe when using v2.6.34-rc1.
> > 
> > Ben, can you queue the fix below from Tony for -rc2?
> 
> The original patch attached again below.
> 
FWIW,

Tony's "[PATCH] i2c-omap: Fix reg_shift init" makes the mainline
2.6.34-rc1 booting on OMAP3.

Tested-by: Jarkko Nikula <jhnikula@gmail.com>

      parent reply	other threads:[~2010-03-19  9:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-13  1:54 [PATCH v2] [I2C-OMAP] Add support for 16-bit registers Cory Maccarrone
     [not found] ` <1260669242-29865-1-git-send-email-darkstar6262-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-01-09 17:47   ` Cory Maccarrone
2010-01-09 18:33     ` Tony Lindgren
2010-01-09 18:35       ` Cory Maccarrone
     [not found]         ` <6cb013311001091035x54321b3aqb814f476200980af-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-12  1:28           ` Tony Lindgren
     [not found]             ` <20100112012814.GK5055-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2010-01-12  1:50               ` Cory Maccarrone
     [not found]                 ` <6cb013311001111750m17430092p8d9bd1102152db8b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-02  0:07                   ` Tony Lindgren
2010-03-10 18:04               ` Kevin Hilman
     [not found]                 ` <87k4tkf3ye.fsf-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
2010-03-10 22:30                   ` Tony Lindgren
     [not found]                     ` <20100310223000.GT2900-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2010-03-11 16:40                       ` Kevin Hilman
     [not found]                         ` <878w9ydd6x.fsf-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
2010-03-12  0:17                           ` Tony Lindgren
     [not found]                             ` <20100312001753.GC2900-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2010-03-13  0:28                               ` Kevin Hilman
2010-03-15 18:56                             ` Kevin Hilman
2010-03-19  9:05                     ` Jarkko Nikula [this message]

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=20100319110509.76784df2.jhnikula@gmail.com \
    --to=jhnikula@gmail.com \
    --cc=ben-linux@fluff.org \
    --cc=darkstar6262@gmail.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).