From: Kevin Hilman <khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
To: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
Cc: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>,
Cory Maccarrone
<darkstar6262-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2] [I2C-OMAP] Add support for 16-bit registers
Date: Fri, 12 Mar 2010 16:28:00 -0800 [thread overview]
Message-ID: <87eijp2hgv.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20100312001753.GC2900-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org> (Tony Lindgren's message of "Thu\, 11 Mar 2010 16\:17\:53 -0800")
Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org> writes:
> * Kevin Hilman <khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org> [100311 08:36]:
>> Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org> writes:
>> >
>> > Anyways, for the future, considering how critical this driver is
>> > for all omaps.. And considering how badly this driver needs some
>> > updates done..
>> >
>> > How about we pile up the i2c-omap patches for testing into linux-omap
>> > branch first, then ask Ben to pull it around -rc6 after we've all
>> > acked and tested the changes?
>> >
>> > Ben does that sound OK to you?
>>
>> Here's another one to add to omap-testing then.
>>
>> This one has been submitted to linux-i2c a couple times and been in
>> the OMAP PM branch for a while.
>
> OK, let's add that to omap-testing after we're done with the initial
> fixes. This does not currently apply on top of omap-testing, BTW.
The patch is against v2.6.34-rc1.
Kevin
next prev parent reply other threads:[~2010-03-13 0:28 UTC|newest]
Thread overview: 15+ 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 [this message]
2010-03-15 18:56 ` Kevin Hilman
2010-03-19 9:05 ` Jarkko Nikula
2010-01-11 23:29 ` [APPLIED] " Tony Lindgren
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=87eijp2hgv.fsf@deeprootsystems.com \
--to=khilman-1d3hcaltpluheniveurvkkeocmrvltnr@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=darkstar6262-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.