All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Kevin Hilman <khilman@ti.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	John Stultz <johnstul@us.ibm.com>,
	Andy Green <andy.green@linaro.org>
Subject: Re: [PATCH] ARM: OMAP2+: omap_device: call all suspend, resume callbacks when OMAP_DEVICE_NO_IDLE_ON_SUSPEND is set
Date: Mon, 5 Mar 2012 12:52:33 -0800	[thread overview]
Message-ID: <20120305205233.GT12083@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1203051312390.1430@utopia.booyaka.com>

* Paul Walmsley <paul@pwsan.com> [120305 11:44]:
> On Mon, 5 Mar 2012, Kevin Hilman wrote:
> 
> > Tony, this fix is needed for v3.3.
> 
> Of course, I don't have any objection to this patch going into the v3.3-rc 
> kernels.  But given that some maintainers seem to be pushing back against 
> late -rc patches, this one could probably be delayed to 3.4 if required.  
> no_console_suspend is a debugging-only option and bugs involving it are 
> unlikely to affect most users.

I'm fine with your queueing it for v3.4 merge window.

Regards,

Tomny

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2+: omap_device: call all suspend, resume callbacks when OMAP_DEVICE_NO_IDLE_ON_SUSPEND is set
Date: Mon, 5 Mar 2012 12:52:33 -0800	[thread overview]
Message-ID: <20120305205233.GT12083@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1203051312390.1430@utopia.booyaka.com>

* Paul Walmsley <paul@pwsan.com> [120305 11:44]:
> On Mon, 5 Mar 2012, Kevin Hilman wrote:
> 
> > Tony, this fix is needed for v3.3.
> 
> Of course, I don't have any objection to this patch going into the v3.3-rc 
> kernels.  But given that some maintainers seem to be pushing back against 
> late -rc patches, this one could probably be delayed to 3.4 if required.  
> no_console_suspend is a debugging-only option and bugs involving it are 
> unlikely to affect most users.

I'm fine with your queueing it for v3.4 merge window.

Regards,

Tomny

  reply	other threads:[~2012-03-05 20:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-03 20:15 [PATCH] ARM: OMAP2+: omap_device: call all suspend, resume callbacks when OMAP_DEVICE_NO_IDLE_ON_SUSPEND is set Paul Walmsley
2012-03-03 20:15 ` Paul Walmsley
2012-03-05 15:21 ` Kevin Hilman
2012-03-05 15:21   ` Kevin Hilman
2012-03-05 20:16   ` Paul Walmsley
2012-03-05 20:16     ` Paul Walmsley
2012-03-05 20:52     ` Tony Lindgren [this message]
2012-03-05 20:52       ` Tony Lindgren
2012-03-05 21:15       ` Paul Walmsley
2012-03-05 21:15         ` Paul Walmsley

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=20120305205233.GT12083@atomide.com \
    --to=tony@atomide.com \
    --cc=andy.green@linaro.org \
    --cc=johnstul@us.ibm.com \
    --cc=khilman@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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.