All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
Cc: Jon Hunter <jon-hunter@ti.com>,
	Alexander Aring <a.aring@phytec.de>,
	linux-omap@vger.kernel.org, ben-linux@fluff.org,
	tony@atomide.com, linux-i2c@vger.kernel.org,
	Shubhrajyoti <shubhrajyoti@ti.com>
Subject: Re: [PATCH] i2c_omap: correct OMAP_I2C_SYSC_REG offset
Date: Fri, 09 Dec 2011 10:03:29 -0800	[thread overview]
Message-ID: <874nx9hbbi.fsf@ti.com> (raw)
In-Reply-To: <4EE1AEA8.6000008@ti.com> (shubhrajyoti@ti.com's message of "Fri, 09 Dec 2011 12:16:00 +0530")

Ben,

[...]

>>> Shubhrajyoti/Jon, any objections to me queuing this fix for v3.2 (and
>>> stable.)  It would just mean rebasing your other fixes and cleanup
>>> series on top of this.
>>
>> I have no issue with that and I am in favour of getting the fix in now.
> I too have no issues.

I've queued this fix in my i2c fixes branch[1], and added a 
Cc: stable@kernel.org so it makes it into stable as well.

Note, This branch also includes the other fix I sent a couple days
ago[2], so pulling this branch will get you all the OMAP I2C fixes for
v3.2.

Thanks,

Kevin

[1]
git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git for_3.2/fixes/i2c

[2] Subject: [PATCH] I2C: OMAP: fix FIFO usage for OMAP4.

      parent reply	other threads:[~2011-12-09 18:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-08 14:43 [PATCH] i2c_omap: correct OMAP_I2C_SYSC_REG offset Alexander Aring
     [not found] ` <1323355433-8508-1-git-send-email-a.aring-guT5V/WYfQezQB+pC5nmwQ@public.gmane.org>
2011-12-08 18:12   ` Kevin Hilman
     [not found]     ` <87obvjj5l5.fsf-l0cyMroinI0@public.gmane.org>
2011-12-08 19:31       ` Jon Hunter
     [not found]         ` <4EE11091.20404-l0cyMroinI0@public.gmane.org>
2011-12-09  6:46           ` Shubhrajyoti
     [not found]             ` <4EE1AEA8.6000008-l0cyMroinI0@public.gmane.org>
2011-12-09 17:51               ` Kevin Hilman
2011-12-09 18:03             ` Kevin Hilman [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=874nx9hbbi.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=a.aring@phytec.de \
    --cc=ben-linux@fluff.org \
    --cc=jon-hunter@ti.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=shubhrajyoti@ti.com \
    --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 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.