From: Shubhrajyoti <shubhrajyoti@ti.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: Shubhrajyoti Datta <omaplinuxkernel@gmail.com>,
linux-omap@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, ben-linux@fluff.org,
tony@atomide.com, Kevin Hilman <khilman@ti.com>
Subject: Re: [PATCHv10 00/11] I2C fixes
Date: Mon, 11 Jun 2012 23:09:34 +0530 [thread overview]
Message-ID: <4FD62D56.2020500@ti.com> (raw)
In-Reply-To: <20120611160034.GA3887@pengutronix.de>
On Monday 11 June 2012 09:30 PM, Wolfram Sang wrote:
>> Agree,
>> > These are only fixes can it be considered for rc3?
> "Baking in linux-next" and "considering rc3" don't match; baking needs
> time, rc3 is soon. I've put the patches now into my -next branch for
> more exposure.
Thanks.
> I am still uncertain if they should be in 3.5 already;
> there seem to be worhty fixes in there, but they do depend on stuff
> which don't really qualify as bugfixes...
WARNING: multiple messages have this Message-ID (diff)
From: shubhrajyoti@ti.com (Shubhrajyoti)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv10 00/11] I2C fixes
Date: Mon, 11 Jun 2012 23:09:34 +0530 [thread overview]
Message-ID: <4FD62D56.2020500@ti.com> (raw)
In-Reply-To: <20120611160034.GA3887@pengutronix.de>
On Monday 11 June 2012 09:30 PM, Wolfram Sang wrote:
>> Agree,
>> > These are only fixes can it be considered for rc3?
> "Baking in linux-next" and "considering rc3" don't match; baking needs
> time, rc3 is soon. I've put the patches now into my -next branch for
> more exposure.
Thanks.
> I am still uncertain if they should be in 3.5 already;
> there seem to be worhty fixes in there, but they do depend on stuff
> which don't really qualify as bugfixes...
next prev parent reply other threads:[~2012-06-11 17:39 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 10:56 [PATCHv10 00/11] I2C fixes Shubhrajyoti D
2012-05-29 10:56 ` Shubhrajyoti D
2012-05-29 10:56 ` [PATCHv10 05/11] I2C: OMAP: Don't check if wait_for_completion_timeout() returns less than zero Shubhrajyoti D
2012-05-29 10:56 ` Shubhrajyoti D
[not found] ` <1338288983-15026-1-git-send-email-shubhrajyoti-l0cyMroinI0@public.gmane.org>
2012-05-29 10:56 ` [PATCHv10 01/11] I2C: OMAP: make omap_i2c_unidle/idle functions depend on CONFIG_PM_RUNTIME Shubhrajyoti D
2012-05-29 10:56 ` Shubhrajyoti D
2012-05-29 10:56 ` [PATCHv10 02/11] I2C: OMAP: Fix the mismatch of pm_runtime enable and disable Shubhrajyoti D
2012-05-29 10:56 ` Shubhrajyoti D
2012-05-29 10:56 ` [PATCHv10 03/11] I2C: OMAP: Fix the interrupt clearing in OMAP4 Shubhrajyoti D
2012-05-29 10:56 ` Shubhrajyoti D
2012-05-29 10:56 ` [PATCHv10 04/11] I2C: OMAP: Prevent the register access after pm_runtime_put in probe Shubhrajyoti D
2012-05-29 10:56 ` Shubhrajyoti D
2012-05-29 10:56 ` [PATCH 06/11] I2C: OMAP: Fix the crash in i2c remove Shubhrajyoti D
2012-05-29 10:56 ` Shubhrajyoti D
2012-05-29 10:56 ` [PATCH 07/11] I2C: OMAP: Handle error check for pm runtime Shubhrajyoti D
2012-05-29 10:56 ` Shubhrajyoti D
2012-06-27 1:43 ` Kevin Hilman
2012-06-27 1:43 ` Kevin Hilman
[not found] ` <874npxv8aj.fsf-l0cyMroinI0@public.gmane.org>
2012-06-27 9:01 ` Shubhrajyoti Datta
2012-06-27 9:01 ` Shubhrajyoti Datta
2012-05-29 10:56 ` [PATCHv10 09/11] I2C: OMAP: Do not set the XUDF(Transmit underflow) if the underflow is not reached Shubhrajyoti D
2012-05-29 10:56 ` Shubhrajyoti D
2012-05-29 10:56 ` [PATCHv10 10/11] I2C: OMAP: Rename the 1p153 to the erratum id i462 Shubhrajyoti D
2012-05-29 10:56 ` Shubhrajyoti D
2012-05-29 10:56 ` [PATCHv10 08/11] I2C: OMAP: prevent the overwrite of the errata flags Shubhrajyoti D
2012-05-29 10:56 ` Shubhrajyoti D
2012-05-29 10:56 ` [PATCHv10 11/11] OMAP/I2C - Fix timeout problem during suspend Shubhrajyoti D
2012-05-29 10:56 ` Shubhrajyoti D
2012-05-31 22:59 ` [PATCHv10 00/11] I2C fixes Kevin Hilman
2012-05-31 22:59 ` Kevin Hilman
2012-06-10 5:40 ` Shubhrajyoti Datta
2012-06-10 5:40 ` Shubhrajyoti Datta
2012-06-11 16:00 ` Wolfram Sang
2012-06-11 16:00 ` Wolfram Sang
2012-06-11 17:39 ` Shubhrajyoti [this message]
2012-06-11 17:39 ` 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=4FD62D56.2020500@ti.com \
--to=shubhrajyoti@ti.com \
--cc=ben-linux@fluff.org \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=omaplinuxkernel@gmail.com \
--cc=tony@atomide.com \
--cc=w.sang@pengutronix.de \
/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.